GNOME Bugzilla – Bug 397715
Lockdown : Restrict Application Lanching
Last modified: 2021-06-18 15:30:18 UTC
As per mail posted to d-d-l WRT new gconf keys for locking down menu structure via the use of two new gconf keys, restrict_application_launching, and allowed_applications. This bug is to extend this functionality into nautilus, namely when a user double clicks on an application of restricted_application_launching is enabled and the application is not in the allowed list, then it does not launch. See bugs : http://bugzilla.gnome.org/show_bug.cgi?id=394249 http://bugzilla.gnome.org/show_bug.cgi?id=394252 http://bugzilla.gnome.org/show_bug.cgi?id=395887
Created attachment 80531 [details] [review] Proposed feature patch
Created attachment 91629 [details] [review] Updated Patch Updated feature request patch which applies to svn trunk
Created attachment 99475 [details] [review] Feature Patch Updated feature patch for 2.20.1 svn trunk.
Created attachment 99489 [details] [review] Upded Feature Patch This patch obsoletes Matt's Feature Patch as it adds support for reloading extensions menus after disable-command-line has changed
Created attachment 99490 [details] [review] open-terminal patch Support locking down "Open Terminal" menu item.
Is this going in?
Created attachment 148770 [details] updated patch We no longer apply the patch described in comment #5. This was already fixed upstream, I believe as a part of bug #477263. Note that the patch in comment #4 has been reworked to apply against the latest release. The updated version of the patch is attached. Can this go upstream? Initially it sounded like there was community interest in getting this working, and this code has been soaking for a long time in our Solaris releases. For the most part, people seem to use this feature and find it useful. We have been updating this patch as we have resolved bugs, so I think at this point this code is working well enough for general use (and lockdown is not a feature which is on by default anyway).
Created attachment 148800 [details] [review] updated patch Sorry, in my last comment I attached the wrong patch. Here is the correct latest patch. This replaces the patch in comment #4.
Comment on attachment 148800 [details] [review] updated patch libnautilus-private/nautilus-lockdown.c does not exist anymore in git master. Hence setting 'needs-rework' as patch does not apply cleanly.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version of Files (nautilus), then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/nautilus/-/issues/ Thank you for your understanding and your help.