Timeline for How does the Unix file privilege system differ from that of Windows?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 14, 2011 at 21:51 | comment | added | Logan Capaldo | @George, right just like Unix (unless you want to start arguing about whether looking for a shebang is "advanced" or not). I just wanted to make it clear that the file extension has nothing to do with the security model. If you mark an executable non-executable on Windows it has the same effect it does on a unix. | |
| Jun 14, 2011 at 20:41 | comment | added | Nathan Osman | @Logan: Ah, I see. But that certainly isn't because Windows performs some sort of advanced analysis of the file's header - it simply tries to link and load the file and reports a failure if it cannot. | |
| Jun 14, 2011 at 20:34 | comment | added | Logan Capaldo | @George The same applies to a graphical file manager with a buggy thumb nail previewer on any operating system. My point was that CreateProcess doesn't give two hoots if your program ends in .exe (and this is easy to see by running a program from cmd.exe), but it does indeed care about the execute bit. | |
| Jun 14, 2011 at 19:46 | comment | added | Nathan Osman | @Logan: Actually, they do have significance on Windows. The file extension determines what program(s) can be used to open it as well as indicating to explorer what type of file it is so that thumbnails can be generated. In the latter case, that could potentially exploit a bug that exists in the thumbnail generator and therefore could compromise a system. | |
| May 22, 2011 at 13:13 | comment | added | Logan Capaldo | Extensions don't matter on windows either. | |
| May 22, 2011 at 5:27 | comment | added | Patches | Windows actually does have an executable permission, although they defeat the purpose by setting it by default. | |
| May 21, 2011 at 22:21 | history | answered | user732 | CC BY-SA 3.0 |