Skip navigation.

File Permissions in Nautilus

Nautilus
Nautilus

Alexander Larsson recently committed his work on the permissions page in Nautilus. He writes: I just commited a rework of the permissions page in the file property dialog. It has a simplified UI (and an advanced/unixy version availible via a gconf setting) and support for recursive permission changes.

Screenshot 1 | Screenshot 2 | Screenshot 3 | Screenshot 4

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
GUI ACL Editor eiciel by Anonymous George (not verified)
Thunar by Anonymous George (not verified)
Great Job by Anonymous George (not verified)

ACL, ACL, ACL

Where are you? This is some nice work, but every man and his dog screams for ACL. Why implement a better unix-permission GUI when everybody actually wants ACL.

Agree.

Agree 100%

UNIX permissions **SUCK**!! They are nearly useless in an enterprise environmentmnet.

But that isn't the only thing very wrong with this. The group ownership is a combo box (drop down menu?). What a usability nightmare, when many environments have over a hundred groups (driven in part by UNIX's crappy traditional file permission scheme).

combo-box for groups is unworkable. by Anonymous George (not verified)

ACLs suck

Have you never worked in a corporate environment? ACLs are too complex for most users to grasp, and the operating system is prone to screw things up for you as well. I can't tell how many times I've sat down to reset ACLs ("apply changes to all subfolders and files") because the user or Windows itself has messed things up.

For instance when installing a Terminal Server, all users get write access to all kinds of folders on the server (including c:\). Great job Microsoft! This problem is then compounded by the ACLs in the Windows registry.

We actually run scripts nightly to reset the ACLs on c:\ and critical sections of the registry in order to prevent users from screwing up the system. From my point of view ACLs **suck** compared to UNIX permissions.

Re: ACLs suck

>Have you never worked in a corporate environment?

Nice perjorative! But yes, for more than a decade.

>ACLs are too complex for most users to grasp, and the operating
>system is prone to screw things up for you as well. I can't tell
>how many times I've sat down to reset ACLs ("apply changes to all
>subfolders and files") because the user or Windows itself has messed
>things up.

Funny, we have huge volumes on XFS with ACLs. User's change ACLs on files via the security tab in Windows Explorer. Works great. And the alternative would be? Let user's create POSIX groups?

>For instance when installing a Terminal Server, all users get write >access to all kinds of folders on the server (including c:\). Great >job Microsoft! This problem is then compounded by the ACLs in the >Windows registry.

This has nothing to do with ACLs as a technology. Like the registry, it is a failure of implementation (if indeed it is a failure, we also run TSE without any significant issues).

you are probably an expert by Anonymous George (not verified)

The explanation is the 40 years.

>You sound like an expert, but I just wonder how a system which has been >in use for 40+ years in entreprise environments worldwide can be >"nearly useless".

Because the world changed in 40 years. Machines support more users with more complex relationships.

>Also, ACL, as implemented in windows, result in everyone being >administrator,

Complete and total rubbish.

>because it's so hard to have anything really working with it
>(all the companies I've seen where computers are not only use for
>trivial tasks work this way).

Eh?

>And the unix permissions "suck" so bad that they block most of >security holes... unlike ACLs.

Rubbish.

He's obviously more of an by Anonymous George (not verified)

Override permissions

Fantastic work.
Now the only real issue with permissions is what happens when you don't have permission to copy, move or delete a file. It would be great if nautilus would be integrated with gksudo to allow you to enter a password to force the move/copy instead of showing a mostly useless dialog saying the move failed and forcing you to use the cli.

gksudo integration

This asusme most, or even many, users have access to the administrative password. I doubt this is true. It is a good idea, but would been to be something that could be disabled via gconf.

... by Anonymous George (not verified)
Lets not forget; by Anonymous George (not verified)
The only trolls I've ever by Anonymous George (not verified)

Why

You couldn't have counted my comment, as comment was split, in that I am glad someone was fixing them, but a button should be clearly marked.

You do have a point, in that, I believe that people should reconise that someone worked to make progress for everyone.

Why did users have to clamor about file permissions issues for years?
If people complained about feel permissions for years, and no one did anything, there is something wrong with the way designers/programers are addressing feedback. It would seem that the present system doesn't work, and when people speak up here--you fault them for it.

Why did users have to clamor by Anonymous George (not verified)
Fix this first by Anonymous George (not verified)

Well

I'm the one complaining about ACLs. I really can't feel great about changes in Nautilus, because those changes neglect real needs, concentrating on minor things. They do not really improve situation, there is still to little control in this dialog. I am using ACLs daily, I even succeded at explaining them to my family. But every time ACL operation is needed I have to resort to shell commands. I can't expect other users of my computer to know shell. They know how to change basic permission by clickety-click.
Changes shown above are really cosmetic. Which is really sad by itself, as ACL in Nautilus already got implemented and lost. See http://blogs.sun.com/roller/page/alvaro?entry=nautilus_acl_support

--
:wq

I really can't feel great by Anonymous George (not verified)

I prefer the Dialog with the

I prefer the Dialog with the Checkboxes :) *vote*
Suns ACL Dialog ist horrible, by no chance you could add this to GNOME Mainstream. What happens when you don't have ACL Support? Should the Dialog disappear, or should the tab be inactive?

Nautilus needs a good Plugin Framework so that someone (who needs it) could make an Nautilus-ACL Plugin.

EICIEL, acl for nautilus by Anonymous George (not verified)

Finally!

This has been an open issue for how many years?

Praise the Lard someone has finally attacked this bug and we have a resolution for it.

It has been . . . by Anonymous George (not verified)

ACLs?

I don't see ACL/xattr editing in those screenshots. Aren't they implemented?
And why add completly unneeded and cryptic SELinux context?

--
:wq

RE:ACLs by Anonymous George (not verified)
Why the folder and file by Anonymous George (not verified)
Because if you apply the by Anonymous George (not verified)

Recurse?

Does the "Apply Permissions to Enclosed Folders" button recurses the folders? If that is what it meant to mean, can it be changed? Enclosed in what? It's like a dangling modifier, or an unreferenced object.

Enclosed would seem to indicate: everything inside of something, but it does nothing to imply: everything inside of something, and everything inside of that, and so on.

The word "recursive" is as important concept as a word to understand.

I would rather new users look up the word, or press help, and learn about the nested, parent/child relationship magnatude of the sweeping change they are going to make, than see a word they do recognize used in a new and dreadful way.

There is a second problem: the word folders. It seems to imply: It changes folders, not files, right? Is this what pressing this button will do?

If I understand what that button does, something like "Apply Permissions Recursively" would work better, "Apply Permissions to Nested Folders and Files."

At times, I was dismayed that I had to open a terminal window to do everyday file owner changing, and I'm glad that people are working on things such as these. Thank You.

Completely agree. Don't by Anonymous George (not verified)

Recursive

er, hello? Have you ever tried to explain the concept of recursiveness to people? Remember how long it took before you got it yourself?

I still agree

but "folders" got me confused. Let it say "include contents and subfolders"

Recursive: "It means that

Recursive: "It means that permissions are applied to everything in that folder, even other folders, and their contents, and so on."

Oh yeah, that's just a crazy concept that makes no sense whatsoever. It took how long to explain that?

I had no problem learning it and never had a problem explaining it. Adding new diction that is in no way any less ambiguous is not only poor design but bad cognitive practices. There is nothing wrong with the term "recursive." Why force the issue into two? People either know what recursive does (which are now forced to learn something new; you may see this as trivial but an overabundance of trivial learning adds up) or they don't and are learning something new that is localized only to GNOME.

If you are going to use different terminology make sure it is simply intuitive or just don't use it.

Obviously, people that say by Anonymous George (not verified)
Heh, that was even close to by Anonymous George (not verified)
I like it! by Anonymous George (not verified)