Comment 29 for bug 192629

Revision history for this message
touristguy87 (touristguy87) wrote :

this also is nonsense:

"i suggest using .trash-{user}, and having the contents of that folder appear in the relevant user trash:// folder. if the admin cares about security of files it will be obvious that no files should ever be stored on the ntfs drive (or get rid of the drive), if the admin lets the users store file on this drive, then it is clear that the admin is relying on trust between the users when dealing with files on..."

....don't assume that someone who doesn't know as much as you do agrees with you about what they are doing.
In fact you shouldn't ever assume that another person agrees with you about what they are doing.

In this case the issue is plain and simple. Putting one of my image files in the trash merely by hitting the delete key when I'm looking at the image in the viewer. This has nothing to do with a security issue and no assumptions about security should be made! I just want to delete one of my files on an NTFS partition without having to go into another app to do it, not open that drive up to malicious files.

Forget all this! Just don't even think about this at all. How do I fix this app so that it will move an open image to the trash, if the image is on an NTFS partition which is apparently the problem, assuming one thing: that the image isn't write-protected, that this isn't an issue of file-rights. Period. End of issue.

If it's an issue of file-rights I will be happy to chmod the entire drive.

Thah is not the problem when it tells me that the trash cannot be found.