Score:0

ACL (Access Control List) not working in RHEL 9

pt flag

I'm creating some ACLs in my RHEL 9 laboratory under learning purposes. But I faced the following problem.

As user1 I've created a file named "aclfile" under /tmp and created an ACL so user100 can operate read and write actions over this file.

[user1@server1 tmp]$ pwd
/tmp
[user1@server1 tmp]$ touch aclfile
[user1@server1 tmp]$ setfacl -m u:user100:rw aclfile
[user1@server1 tmp]$ getfacl -c aclfile
user::rw-
user:user100:rw-
group::r--
mask::rw-
other::r--
[user1@server1 tmp]$ ls -l aclfile
-rw-rw-r--+ 1 user1 user1 0 Nov 11 16:42 aclfile

As user100, even with the ACL allowing this user to read and write in the aclfile. Vim, Vi and Nano editors gave me this error message when I try to write(!w,!wq,!x) something in this file: "aclfile" E212: Can't open file for writing".

But, this works out well as user100:

[user100@server1 tmp]$ echo "foo" > aclfile
[user100@server1 tmp]$ cat aclfile
foo

Am I missing any point here?

user122574 avatar
ve flag
I've found the same issue in RHEL9. I also noted that between 8 and 9 the default umask was changed from 0002 to 0022, though, if one does chmod 664 on the file, don't see why that would matter.
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.