<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Droid Sans Mono'; font-size:10pt; font-weight:400; font-style:normal;">On Sunday 22 February 2009, R.F. Pels wrote:<br>
> On Sun 22 February 2009 18.38.21 Michael Pyne wrote:<br>
><br>
> Now for something completely different but still related...<br>
><br>
> > Alexander Larsson is handling the same thing for GNOME, and they have<br>
> > changed their file view to only "sniff" for desktop files that are<br>
> > executable or in the system directory, and only files with a .desktop<br>
> > extension. (http://mail.gnome.org/archives/desktop-devel-list/2009-<br>
> > February/msg00132.html)<br>
><br>
> Hmmm. I've been reading this for a bit, and they used the word<br>
> 'trusted'. That set my mind in gear as to how we can make it possible to<br>
> indeed mark an executable (in whatever form or shape) as trusted.<br>
> Something like signing it perhaps?<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>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).<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Regards,<br>
- Michael Pyne</p></body></html>