<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Thank you both, now I have a clearer picture.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof ContentPasted0">
Actually, the ACL and umask interaction was unclear to me. Reading around I also found some reference in the man page of the open syscall ("in the absence of a default ACL, the mode of the created file is (mode & ~umask)").</div>
<div class="elementToProof">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Cheers,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Ivano</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature">
<div>
<div id="divtagdefaultwrapper" dir="ltr" style="font-size: 12pt; font-family: Calibri, Helvetica, sans-serif; color: rgb(0, 0, 0);">
</div>
<div dir="ltr" style="font-size: 12pt; font-family: Calibri, Helvetica, sans-serif; color: rgb(0, 0, 0);">
<p><span id="ms-rterangepaste-start"></span></p>
<div>__________________________________________</div>
<div>Paul Scherrer Institut</div>
<div>Ivano Talamo</div>
<div>WHGA/038</div>
<div>Forschungsstrasse 111</div>
<div>5232 Villigen PSI</div>
<div>Schweiz</div>
<div><br>
</div>
<div>Phone: +41 56 310 47 11</div>
<div>E-Mail: ivano.talamo@psi.ch</div>
<span id="ms-rterangepaste-end"></span><br>
<p></p>
</div>
</div>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> gpfsug-discuss <gpfsug-discuss-bounces@gpfsug.org> on behalf of Christof Schmitt <christof.schmitt@us.ibm.com><br>
<b>Sent:</b> 15 September 2023 01:44<br>
<b>To:</b> gpfsug-discuss@gpfsug.org <gpfsug-discuss@gpfsug.org><br>
<b>Subject:</b> Re: [gpfsug-discuss] Unexpected permissions with ACLs</font>
<div> </div>
</div>
<div lang="EN-US" style="text-align:left; direction:ltr">
<div>Yes. If there is one ACL entry that is inherited to a new file/directory, then only that inherited entry will be in the ACL of the new file/directory. The special case here is now that there is one inheritable entry, but that is flagged with DirInherit,
so it does not apply to new files.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christof</div>
<div><br>
</div>
<div>On Thu, 2023-09-14 at 21:13 +0000, Losen, Stephen C (scl) wrote:</div>
<blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid; padding-left:1ex">
<div style="display:none!important; display:none; visibility:hidden; font-size:1px; color:#ffffff; line-height:1px; height:0px; max-height:0px; opacity:0; overflow:hidden">
Hi, you have specified an inherited (inherit only) ACE in the parent directory’s ACL, so that disables umask. New files will only get whatever ACEs they inherit. Since the only inherited ACE pertains to directories and not files, a new file
</div>
<div style="display:none!important; display:none; visibility:hidden; font-size:1px; color:#ffffff; line-height:1px; height:0px; max-height:0px; opacity:0; overflow:hidden">
ZjQcmQRYFpfptBannerStart</div>
<div dir="ltr" lang="en" id="x_pfptBannerrlayzqe" style="display:block!important; text-align:left!important; margin:16px 0px 16px 0px!important; padding:8px 16px 8px 16px!important; border-radius:4px!important; min-width:200px!important; background-color:#D0D8DC!important; background-color:#D0D8DC; border-top:4px solid #90a4ae!important; border-top:4px solid #90a4ae">
<div id="x_pfptBannerrlayzqe" style="float:left!important; display:block!important; margin:0px 0px 1px 0px!important; max-width:600px!important">
<div id="x_pfptBannerrlayzqe" style="display:block!important; visibility:visible!important; background-color:#D0D8DC!important; color:#000000!important; color:#000000; font-family:'Arial',sans-serif!important; font-family:'Arial',sans-serif; font-weight:bold!important; font-weight:bold; font-size:14px!important; line-height:18px!important; line-height:18px">
This Message Is From an External Sender </div>
<div id="x_pfptBannerrlayzqe" style="display:block!important; visibility:visible!important; background-color:#D0D8DC!important; color:#000000!important; color:#000000; font-weight:normal; font-family:'Arial',sans-serif!important; font-family:'Arial',sans-serif; font-size:12px!important; line-height:18px!important; line-height:18px; margin-top:2px!important">
This message came from outside your organization. </div>
</div>
<div id="x_pfptBannerrlayzqe" style="float:right!important; display:block!important; display:block; margin:0px 0px 0px 16px!important; text-align:right!important; width:fit-content!important">
<a id="x_pfptBannerrlayzqe" href="https://us-phishalarm-ewt.proofpoint.com/EWT/v1/PjiDSg!2Y-vrJ9RxDnU-mYbFsElzTntwzTT-DfGSCnfv-QAUYaAOnlLm4fXFBf20DlV_V763N-syTtqyssyVlwdUuQ4A_i6JoPRMlLqcdY4sTzfjvU$" style="display:inline-block!important; text-decoration:none">
<div class="x_pfptPrimaryButtonrlayzqe" style="display:inline-block!important; display:inline-block; visibility:visible!important; opacity:1!important; color:#000000!important; color:#000000; font-family:'Arial',sans-serif!important; font-family:'Arial',sans-serif; font-size:14px!important; font-weight:normal!important; text-decoration:none!important; border-radius:2px!important; padding:7.5px 16px!important; margin:3px 0 3px 16px!important; white-space:nowrap!important; width:fit-content!important; border:1px solid #666666">
Report Suspicious </div>
</a></div>
<div style="clear:both!important; display:block!important; visibility:hidden!important; line-height:0!important; font-size:0.01px!important; height:0px">
</div>
</div>
<div style="display:none!important; display:none; visibility:hidden; font-size:1px; color:#ffffff; line-height:1px; height:0px; max-height:0px; opacity:0; overflow:hidden">
ZjQcmQRYFpfptBannerEnd</div>
<style>
<!--
#x_pfptBannerrlayzqe
{display:block!important;
visibility:visible!important;
opacity:1!important;
background-color:#D0D8DC!important;
max-width:none!important;
max-height:none!important}
-->
</style>
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
span.x_EmailStyle19
{font-family:"Calibri",sans-serif;
color:windowtext}
.x_MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.x_WordSection1
{}
-->
</style>
<div class="x_WordSection1">
<p class="x_MsoNormal">Hi, you have specified an inherited (inherit only) ACE in the parent directory’s ACL, so that disables umask. New files will only get whatever ACEs they inherit. Since the only inherited ACE pertains to directories and not files, a new
file inherits no ACEs, and hence ends up with zero permissions (which I suspect is no ACEs at all in its ACL).</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">So you need to specify some inherited ACEs for files as well as directories. Or else use FileInherit:DirInherit:InheritOnly</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">If the parent directory has no inherited ACEs in its ACL then the permissions on new files/directories are controlled by umask.</p>
<div>
<div>
<div>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Steve Losen</p>
<p class="x_MsoNormal">Research Computing</p>
<p class="x_MsoNormal">University of Virginia</p>
<p class="x_MsoNormal"><a href="mailto:scl@virginia.edu"><span style="color:#0563C1">scl@virginia.edu</span></a> 434-924-0640</p>
</div>
</div>
</div>
<p class="x_MsoNormal"> </p>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="x_MsoNormal"><b><span style="font-size:12.0pt; color:black">From: </span>
</b><span style="font-size:12.0pt; color:black">gpfsug-discuss <gpfsug-discuss-bounces@gpfsug.org> on behalf of Talamo Ivano Giuseppe <ivano.talamo@psi.ch><br>
<b>Reply-To: </b>gpfsug main discussion list <gpfsug-discuss@gpfsug.org><br>
<b>Date: </b>Thursday, September 14, 2023 at 3:19 PM<br>
<b>To: </b>"gpfsug-discuss@gpfsug.org" <gpfsug-discuss@gpfsug.org><br>
<b>Subject: </b>Re: [gpfsug-discuss] Unexpected permissions with ACLs</span></p>
</div>
<div>
<p class="x_MsoNormal"> </p>
</div>
<div>
<p class="x_MsoNormal"><span style="font-size:12.0pt; color:black"> </span></p>
</div>
<div class="x_MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</div>
<div id="x_divRplyFwdMsg">
<p class="x_MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> gpfsug-discuss <gpfsug-discuss-bounces@gpfsug.org> on behalf of Christof Schmitt <christof.schmitt@us.ibm.com><br>
<b>Sent:</b> 14 September 2023 18:02<br>
<b>To:</b> gpfsug-discuss@gpfsug.org <gpfsug-discuss@gpfsug.org><br>
<b>Subject:</b> Re: [gpfsug-discuss] Unexpected permissions with ACLs</span> </p>
<div>
<p class="x_MsoNormal"> > following:</p>
</div>
</div>
<div>
<div>
<p class="x_MsoNormal" style="margin-bottom:12.0pt">> <br>
> special:group@:rwx-:allow:DirInherit:InheritOnly<br>
> (X)READ/LIST (X)WRITE/CREATE (X)APPEND/MKDIR (X)SYNCHRONIZE<br>
> (X)READ_ACL (X)READ_ATTR (X)READ_NAMED<br>
> (-)DELETE (X)DELETE_CHILD (X)CHOWN (X)EXEC/SEARCH<br>
> (X)WRITE_ACL (X)WRITE_ATTR (X)WRITE_NAMED<br>
> <br>
> According to the manual, the DirInherit:InheritOnly should guarantee<br>
> that the entry applies only to the new subdirectories but now it is<br>
> also affecting new files in the main dir.<br>
> Is this an expected behavior? <br>
<br>
>From an ACL perspective, yes. "InheritOnly" indicates that this entry<br>
does not grant any permissions on the directory. It is only copied<br>
as an entry to new files or subdirectories created in this directory.<br>
So if this is the only ACL entry, there are indeed no permissions on<br>
this directory.<br>
<br>
You can remove the "InheritOnly" bit, then this would also grant<br>
permission on the directory. Or you can add another ACL entry that<br>
grants permissions on the directory.</p>
</div>
<div>
<p class="x_MsoNormal"> </p>
</div>
<div>
<p class="x_MsoNormal">I may have not been clear enough, but that ACE has only been added to the previous 3 ACEs, so the complete one for the directory is the following:</p>
</div>
<div>
<p class="x_MsoNormal"> </p>
</div>
<div>
<p class="x_MsoNormal">#NFSv4 ACL </p>
<div>
<p class="x_MsoNormal">#owner:root</p>
</div>
<div>
<p class="x_MsoNormal">#group:p15875</p>
</div>
<div>
<p class="x_MsoNormal">special:owner@:rwxc:allow</p>
</div>
<div>
<p class="x_MsoNormal"> (X)READ/LIST (X)WRITE/CREATE (X)APPEND/MKDIR (X)SYNCHRONIZE (X)READ_ACL (X)READ_ATTR (X)READ_NAMED</p>
</div>
<div>
<p class="x_MsoNormal"> (-)DELETE (X)DELETE_CHILD (X)CHOWN (X)EXEC/SEARCH (X)WRITE_ACL (X)WRITE_ATTR (X)WRITE_NAMED</p>
</div>
<div>
<p class="x_MsoNormal"> </p>
</div>
<div>
<p class="x_MsoNormal">special:group@:rwx-:allow</p>
</div>
<div>
<p class="x_MsoNormal"> (X)READ/LIST (X)WRITE/CREATE (X)APPEND/MKDIR (X)SYNCHRONIZE (X)READ_ACL (X)READ_ATTR (X)READ_NAMED</p>
</div>
<div>
<p class="x_MsoNormal"> (-)DELETE (X)DELETE_CHILD (X)CHOWN (X)EXEC/SEARCH (X)WRITE_ACL (X)WRITE_ATTR (X)WRITE_NAMED</p>
</div>
<div>
<p class="x_MsoNormal"> </p>
</div>
<div>
<p class="x_MsoNormal">special:everyone@:----:allow</p>
</div>
<div>
<p class="x_MsoNormal"> (-)READ/LIST (-)WRITE/CREATE (-)APPEND/MKDIR (X)SYNCHRONIZE (X)READ_ACL (X)READ_ATTR (X)READ_NAMED</p>
</div>
<div>
<p class="x_MsoNormal"> (-)DELETE (-)DELETE_CHILD (-)CHOWN (-)EXEC/SEARCH (-)WRITE_ACL (-)WRITE_ATTR (-)WRITE_NAMED</p>
</div>
<div>
<p class="x_MsoNormal"> </p>
</div>
<div>
<p class="x_MsoNormal">special:owner@:rwx-:allow:DirInherit:InheritOnly</p>
</div>
<div>
<p class="x_MsoNormal"> (X)READ/LIST (X)WRITE/CREATE (X)APPEND/MKDIR (X)SYNCHRONIZE (X)READ_ACL (X)READ_ATTR (X)READ_NAMED</p>
</div>
<div>
<p class="x_MsoNormal"> (-)DELETE (X)DELETE_CHILD (X)CHOWN (X)EXEC/SEARCH (X)WRITE_ACL (X)WRITE_ATTR (X)WRITE_NAMED</p>
</div>
<p class="x_MsoNormal"> </p>
</div>
<div>
<p class="x_MsoNormal">So I would expect that the first 3 would still produce a 644 mode on the file. Am I wrong?</p>
</div>
<div>
<p class="x_MsoNormal">Cheers,</p>
</div>
<div>
<p class="x_MsoNormal">Ivano</p>
</div>
</div>
</div>
<pre>_______________________________________________</pre>
<pre>gpfsug-discuss mailing list</pre>
<pre>gpfsug-discuss at gpfsug.org</pre>
<a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org">
<pre>http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org</pre>
</a>
<pre> </pre>
</blockquote>
</div>
</body>
</html>