From kde-core-devel Mon Feb 23 23:34:21 2009 From: Michael Pyne Date: Mon, 23 Feb 2009 23:34:21 +0000 To: kde-core-devel Subject: Re: .desktop security changes are committed Message-Id: <200902231834.25924.mpyne () purinchu ! net> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=123543211409853 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart7698121.1FMcyfLHDN" --nextPart7698121.1FMcyfLHDN Content-Type: multipart/alternative; boundary="Boundary-01=_+JzoJJ8e4QbLn9A" Content-Transfer-Encoding: 7bit --Boundary-01=_+JzoJJ8e4QbLn9A Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable On Sunday 22 February 2009, R.F. Pels wrote: > On Sun 22 February 2009 18.38.21 Michael Pyne wrote: > > Now for something completely different but still related... > > > Alexander Larsson is handling the same thing for GNOME, and they have > > changed their file view to only "sniff" for desktop files that are > > executable or in the system directory, and only files with a .desktop > > extension. (http://mail.gnome.org/archives/desktop-devel-list/2009- > > February/msg00132.html) > > Hmmm. I've been reading this for a bit, and they used the word > 'trusted'. That set my mind in gear as to how we can make it possible to > indeed mark an executable (in whatever form or shape) as trusted. > Something like signing it perhaps? In this case it's merely via where it is installed to I'm sure (I think by= =20 executable he is referring to the .desktop file and not the executable file= =20 directly). Regards, - Michael Pyne --Boundary-01=_+JzoJJ8e4QbLn9A Content-Type: text/html; charset="iso-8859-15" Content-Transfer-Encoding: 7bit On Sunday 22 February 2009, R.F. Pels wrote:
> On Sun 22 February 2009 18.38.21 Michael Pyne wrote:
>
> Now for something completely different but still related...
>
> > Alexander Larsson is handling the same thing for GNOME, and they have
> > changed their file view to only "sniff" for desktop files that are
> > executable or in the system directory, and only files with a .desktop
> > extension. (http://mail.gnome.org/archives/desktop-devel-list/2009-
> > February/msg00132.html)
>
> Hmmm. I've been reading this for a bit, and they used the word
> 'trusted'. That set my mind in gear as to how we can make it possible to
> indeed mark an executable (in whatever form or shape) as trusted.
> Something like signing it perhaps?


In this case it's merely via where it is installed to I'm sure (I think by executable he is referring to the .desktop file and not the executable file directly).


Regards,
- Michael Pyne

--Boundary-01=_+JzoJJ8e4QbLn9A-- --nextPart7698121.1FMcyfLHDN Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEABECAAYFAkmjMoEACgkQqjQYp5Omm0peDgCfUNLeYJ1mxOGktXZFc9yDNK+4 n5YAoKX7foEM27yiXPgDgKqIDOokOQ+E =ELeQ -----END PGP SIGNATURE----- --nextPart7698121.1FMcyfLHDN--