System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Is it bug in ACL on Filesystem RHEL5 ?

 
monu_1
Regular Advisor

Is it bug in ACL on Filesystem RHEL5 ?

Hi all,

I am using RHEL5 and confused with below=>

ACL applied default in RHEL5 and i am login as root.
I just make a folder in / with 777 permission
lets say /chapter5 and touch /chapter5/f1
Now applied ACL on f1 to rwx by user nh1
# setfacl -m u:nh1:rwx f1
when i login as nh1 it's working.
But prob is that when I login as another user like nh2 and write forcefully on f1, why acl giving permission to write on f1?
and most interesting now it has changed file and group ownership of f1 to nh2.

pls suggest.
Thanks in advanced.
MKS
5 REPLIES
palaniappan.sp
Regular Advisor

Re: Is it bug in ACL on Filesystem RHEL5 ?

Hi,
What is the default umask?? in ur m/c.
Did u tried by giving permission to the file /chapter5/f1 (using chiown and chmod) in the normal way?? If it work ing as per requirement.
Then ur filesystem might not support setfacl??
For Further clarification pls see the man page of setfacl
http://linuxcommand.org/man_pages/setfacl1.html

I hope this link will help u to get..

Regds
Palani
Everything is Possible and Anything is Feasible if u try
monu_1
Regular Advisor

Re: Is it bug in ACL on Filesystem RHEL5 ?

hi Palani

default umak is 0022
I am not changing any default permission in /chapter5/f1
ls -la f1
-rw-r--r-- 1 root root 57 Dec 12 16:33 f1

MKS
Ivan Ferreira
Honored Contributor

Re: Is it bug in ACL on Filesystem RHEL5 ?

>> But prob is that when I login as another user like nh2 and write forcefully on f1, why acl giving permission to write on f1?

I think that you are not writing to the file, you are replacing the file, for example, with a redirection. This will be allowed as the parent directory has 777 and that is why the ownership changed.

Remove 777 permissions to the parent directory and try to "modify" the file as nh2 instead of replace the files.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Stuart Browne
Honored Contributor

Re: Is it bug in ACL on Filesystem RHEL5 ?

Are you using ACL's? From what you've said here so far, you're just using standard permissions and file modes.

If you are using extended permissions, please show us the output of 'getfacl -R /chapter5' (assuming 'f1' is the only file is in there).
One long-haired git at your service...
monu_1
Regular Advisor

Re: Is it bug in ACL on Filesystem RHEL5 ?

Thanks all,

I got the answer. i have changed 777 permission /chapter5 to 701 and now set ACL on /chapter5 and f1.It's working now.

Thanks,
MKS