3 ms·
That's not quite accurate. NTFS has fine-grained permissions, including execute (which is independent of read/open). If a program decides to download or save an
by MichaelGG 13y ago
That's not quite accurate. NTFS has fine-grained permissions, including execute (which is independent of read/open). If a program decides to download or save an attachment and leave execute permissions set, then yes, you can execute it.
It'd not be any different on Linux if your email client saved attachments and marked them +x. Now as a matter of defaults, sure Windows is different.
- jve 13y agoOh, thanks for pointing out - actually I thought it would be a pretty good thing to deny executing by default in folders used by Email clients, Instant messengers, browsers and removable drives. Still someone could save file in different location and execute it. Is there a way to identify which program generated specific file? Or perhaps we could solve this by allowing these programs (like Skype.exe) save files only in specific folders. Is that possible?
- MichaelGG 13y agoIt's hard to retroactively implement this model on Win32 desktop apps. Some programs (Skype, for instance) actually create and run executables on-the-fly (for their stupid obfuscation stuff). Files should inherit the folder ACL, so a deny execute on a folder would work nicely, but end up breaking things for users. Microsoft addresses these issues with the "WinRT" platform and sandboxed/appstore model.