Closed NobleKangaroo closed 2 years ago
Thank you for the detailed issue.
I would gladly accept PR fixing that, if you're not up to it, I can do it on my own.
You bet. I'll get one over to ya as soon as I can. Have a couple things to add in some other questions as well. Thanks for the compilation. It's pretty good material.
On September 11, 2022 6:27:10 AM EDT, "Michał Piotrowski" @.***> wrote:
Thank you for the detailed issue.
I would gladly accept PR fixing that, if you're not up to it, I can do it on my own.
-- Reply to this email directly or view it on GitHub: https://github.com/chlebik/rhcsa-practice-questions/issues/29#issuecomment-1242934300 You are receiving this because you authored the thread.
Message ID: @.***>
Regards,
Sent from my Android device with K-9 Mail. Please excuse my brevity.
I believe adding the "default" (d:) flag to the ACL is incorrect; this results in the target user being unable to access the folder.
Creating a new directory
/facl
with 0700 (default /home directory permissions) then assigning the ACL as suggested:However when attempting to access the directory, the specified user cannot access it.
This is likely due to the user (centos) not having write access already in place, but only on newly created files/directories. Adding
u:centos:rwx
without the precedingd:
resolves this:Confirming access:
Resultant ACL: (note the additional
user:centos:rwx
)After removing all ACLs and starting anew, another way to do this in one fell swoop (if you must use the
d:
prefix) is: