requiring .desktop files to be executable ?

[David Faure]

On Wednesday 18 February 2009, John Tapsell wrote:
> 2009/2/18 David Faure <faure at kde.org>:
> > On Wednesday 18 February 2009, John Tapsell wrote:
> >> 2009/2/18 Michael Pyne <mpyne at purinchu.net>:
> >> > On Tuesday 17 February 2009, John Tapsell wrote:
> >> >> Let's not let this thread die again. It is really important to come
> >> >> to a solution.
> >> >>
> >> >> How about allowing execution if any of following conditions are set:
> >> >> * x-bit it set
> >> >> * owned by root
> >> >> * In a standard path
> >
> > Sounds good to me.
> >
> >> > Why allow both root exception and std path exception? It seems to me that
> >> > they cover the same case.
> >
> > No they don't, my $KDEDIR is not owned by root, and yet I don't want to have
> > to +x every single desktop in it ;-)
> >
> >> How about allowing execution if any of following conditions are set:
> >> * x-bit it set
> >> * owned by root, and not writable by current user (if they aren't root)
> >> * In a standard path, not writable by current user (if they aren't root)
> >
> > I don't see what's "bad" about writable by current user.
> > And again this would break the user-owned $KDEDIR case.
> 
> I was just thinking of the case where Desktop is a fat32 partition
> (usb key, nfs, or something) so the files are all owned by root and
> are writable.

We could remove the "owned by root" from the initial list above, then.
Users rarely go in /usr/something/notstandard and click on .desktop files...
I think it's enough to allow execution of desktop files from
`kde4-config --path xdgdata-apps`.

-- 
David Faure, faure at kde.org, sponsored by Qt Software @ Nokia to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).