Written by Ivo Georgiev the 14 Feb 09 at 08:23.
Related project: Gnome.
New
The .desktop files introduce a lot of problems - users can execute code without knowing what they do.
For example, they can receive the .desktop file on their email, and it's not required to give it execute permissions to run it.
In Gnome, there is a really big issue: .desktop files in ~/.local/share can overwrite the menu entry of some .desktop files in /usr/share/applications. For example, you have Synaptic. The run command specified in the .desktop file placed in /usr/share/applications is "gksu /usr/sbin/synaptic". A virus can copy this .desktop file to ~/.local/share/applications and change the run command to:
gksu /usr/sbin/synaptic. So, the user thinks that he is starting synaptic, but he is executing bad code as root as well as synaptic.
In KDE (tested in 3.5.10) there is another issue, that is fixed in Gnome: KDE doesn't check for MIME type and extension conflicts, so the user might download a file with a .pdf extension (for example), the file can have a icon of a pdf file (since it's a .desktop file, custom icon is easy to put), and click on it, thinking that it's a pdf file. But the file might execute malicious code and also copy itself in the KDE/Gnome autostart directory, or made to be run with root privileges when starting something with gksu for example.
Written by firexq the 5 Mar 09 at 07:05.
Global category: Security.
New
The default encryption scheme in Ubuntu requires that I make a key and store it on a keyring to use... this is all well and good. However, there are times when a user will want to encrypt a file without the key being stored anywhere but his head. With the current system you need to have the decryption key saved, and even if you delete it afterwards, it's still theoretically recoverable.