First work on .desktop file brouhaha [PATCH]

[John Tapsell]

2009/2/19 Michael Pyne <mpyne at purinchu.net>:
> On Thursday 19 February 2009, John Tapsell wrote:
>> 2009/2/19 Michael Pyne:
>> > * If still not, could the user create the file? If not allow it.
>>
>> Maybe allow only if the user can't write to it _and_ it's owned by
>> root? I can't think of a problem with your way, but.. I feel a bit
>> uneasy. Taking _away_ write permissions shouldn't suddenly allow the
>> desktop file to be executed.
>
> Why not, adding execute permissions does. :P
>
> At least the idea so far from my point of view is that we want to make sure
> that simply saving a .desktop file doesn't result in a trojan that you can
> execute with one click, so we require it to be executable. Removing the
> write bit or adding the executable bit is still just one permission
> modification needed to allow a trojan .desktop file to execute.

Yeah, but it can be quite easy to suddenly not have write permission.
Especially if it's from a remote server, or lockable usb key, or if
someone else saved it  (imagine several people sharing a desktop).
How about root owned + not writable or something?