After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 477263 - nautilus doesn't support /desktop/gnome/lockdown/disable_command_line
nautilus doesn't support /desktop/gnome/lockdown/disable_command_line
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-15 17:33 UTC by Kamil J. Dudek
Modified: 2009-07-29 00:31 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch (7.57 KB, patch)
2009-07-28 15:31 UTC, Vincent Untz 		committed Details | Review

Description Kamil J. Dudek 2007-09-15 17:33:14 UTC 
Please describe the problem:
Pessulus has an option of disabling the Command Executing. It locks down Terminal and "Run application" windows. But by right-clicking on desktop, you can easily create an activator to any command you want.

This problem and a Menu Editor one (bug 333222) are these that make my security work more complicated.

Steps to reproduce:
1. Run Pessulus and lock down the Command Prompt
2. Right-click on Desktop
3. Choose "Create an activator"
4. A possibility of exeucting command appeared


Actual results:
4. A possibility of exeucting command appeared

Expected results:
There should be no such option in Desktop context menu after locking the prompt down.

Does this happen every time?
Yes

Other information:
Maybe there should be a proper GConf key in //Desktop/gnome/lockdow like disable_activators ?
Comment 1 Vincent Untz 2009-07-28 14:53:41 UTC 
This is a bug in nautilus: it should check /desktop/gnome/lockdown/disable_command_line and only show the "Create launcher" menu item if it's not True.
Comment 2 Vincent Untz 2009-07-28 15:31:34 UTC 
Created attachment 139391 [details] [review]
Patch

Works fine here.
Comment 3 A. Walton 2009-07-28 22:58:12 UTC 
Patch looks great Vincent.
Comment 4 Vincent Untz 2009-07-29 00:31:04 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.