On Sun, 2007-05-13 at 15:00 +0000, Sebastien Bacher wrote: > The default would be on cancel and the text explains to user that they > are trying to open a file which has a content different of what the > filename indicates which could be a trojan
That risk could only ever occur if one tries to run a program/script. In which case, issuing a warning that a program/script is about to be executed would be more appropriate and prevents this "bug" occuring for all other filetypes. The real culprit here is simply that the feature is looking for a difference between what type the file is and what type a windows user will think the file is, when it should be looking for a difference between whether the file is a script/program to be executed and whether a user will expect a script/program to be started. Most users shouldn't be running programs by double-clicking files in a filesystem browser so I can't see that it is a sensible default. IMHO, the ideal solution would be not to run programs and scripts but rather open a metadata viewer with an execute feature. Same should go for debs, too - open a metadata viewer which I think is what happens already. That makes it clear to the user what the real type is and requires that they be explicit that they want to run the program/install the package. In that case I think the current feature should be limited to scripts/elf/pe/debs etc and a spec started to stop running things on double-click for the future. What do you think? -- Tristan Wibberley -- nautilus's clever anti-hax0r detection is really dumb https://bugs.launchpad.net/bugs/19101 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
