Re: [PMH] Re: [Nautilus-list] Idea for Nautilus and GMC.
- From: John Sullivan <sullivan eazel com>
- To: Miguel de Icaza <miguel ximian com>, Vladimir Vukicevic <vladimir ximian com>
- Cc: Dan Winship <danw ximian com>, <nautilus-list eazel com>, <mc gnome org>, <prion-me-harder ximian com>
- Subject: Re: [PMH] Re: [Nautilus-list] Idea for Nautilus and GMC.
- Date: Thu, 24 May 2001 18:35:38 -0700
There is currently a feature in the gnome-vfs-mime code that's for this kind
of thing: gnome_vfs_mime_can_be_executable (const char *mime_type). There's
a setter too, though in typical use this is set only by reading the mime
data from disk (look for can_be_executable in gnome-vfs.keys).
We added this to avoid problems such as trying to execute an image file
because it had the execute bit inadvertently set.
John
on 5/24/01 6:11 PM, Miguel de Icaza at miguel ximian com wrote:
>
> I just thought of something. Maybe we should have a property in the
> mime-type that describes whether this mime-type is safe to be launched
> or not. So we can manually tag things that might introduce a security
> risk.
>
>> I still don't see the utility in adding hacks into evolution to
>> special-case this. Will the same happen with application/x-rpm? And
>> application/x-scripting-language? I still maintain that having the user
>> have to manually set the execute bit will at least force them to
>> actually have to -do- something that will hopefully make them realize
>> that they either know what they're doing or they don't. It's such a
>> small thing that can possibly prevent a large amount of headache.
>>
>
> _______________________________________________
> Nautilus-list mailing list
> Nautilus-list lists eazel com
> http://lists.eazel.com/mailman/listinfo/nautilus-list
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]