23.12.2022, 14:37
Sorry, I never intended the title to be lurid. Updated.
My recommendation would be to mark and recognize Hybrid's own temporary files and delete them only, without any way to delete an arbitrary folder. For example, you could store the temp files in a folder "_HYBRID_TEMP", or prefix folders with "HYBRID_TEMP_...", and only delete these folders which you're sure are Hybrid, not the user's personal files. Of course, this will likely be a major change in the way Hybrid works, so I do not expect it, but I think this is the proper solution. I think allowing Hybrid to delete an arbitrary folder specified by the user will always hold a risk like the one in this post.
Regarding recovery, sadly this barely works if you have a modern SSD with TRIM enabled.
Thanks!
My recommendation would be to mark and recognize Hybrid's own temporary files and delete them only, without any way to delete an arbitrary folder. For example, you could store the temp files in a folder "_HYBRID_TEMP", or prefix folders with "HYBRID_TEMP_...", and only delete these folders which you're sure are Hybrid, not the user's personal files. Of course, this will likely be a major change in the way Hybrid works, so I do not expect it, but I think this is the proper solution. I think allowing Hybrid to delete an arbitrary folder specified by the user will always hold a risk like the one in this post.
Regarding recovery, sadly this barely works if you have a modern SSD with TRIM enabled.
Thanks!