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 707484 - Permissions dialog missing selective Execute configuration (was removed in commit)
Permissions dialog missing selective Execute configuration (was removed in co...
Status: RESOLVED DUPLICATE of bug 692083
Product: nautilus
Classification: Core
Component: File Properties Dialog
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-09-04 16:28 UTC by greg
Modified: 2016-11-24 19:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description greg 2013-09-04 16:28:57 UTC
Commit 87cfa404d845cbd59b7bf5c95931aa930dbe3d15 (patch) removed the "Show Advanced Permissions" dconf-editor setting. This removal resulted in the removal of an important configuration that the default Permissions dialog does not have: users cannot give a file Owner execute-capability to the exclusion of Group & Others.

Without the "advanced permissions" view, setting Execute on a file necessarily means giving execute-power to 1)Owner 2)Group and 3)Others--something that is not only frustrating but also a security risk. With "advanced permissions" view, Execute can be assigned to only the Owner.

My strong preference is to bring back the "Show Advanced Permissions" dialog as this was one of the most useful features of Nautilus. But more importantly, the Show-Advanced-Permissions dialog should never have been removed leaving in place an inferior/incomplete means for Permissions-configuration.

More information here:
https://bugzilla.gnome.org/show_bug.cgi?id=702685
Comment 1 Alexandre Franke 2016-11-24 19:58:34 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 692083 ***