Patch-ID# 106038-01
Keywords: ACL umask mkdir
Synopsis: SunOS 5.5.1: /usr/bin/mkdir patch
Date: Apr/09/98

Solaris Release: 2.5.1

SunOS Release: 5.5.1

Unbundled Product: 

Unbundled Release: 

Xref: This patch available for x86 as patch 106039

Topic: SunOS 5.5.1: /usr/bin/mkdir patch

	NOTE:	To get the complete fix for 1237009 (users umask modifies 
		ACL's of new files under default ACL's) and 4073684 (mkdir
		-p dir" and "mkdir dir" work differently in the presence 
		of default ACLs), one should install 103640-19 (KU patch)
		or newer.

BugId's fixed with this patch: 1237009 4073684 

Changes incorporated in this version: 

Relevant Architectures: sparc

Patches accumulated and obsoleted by this patch:  

Patches which conflict with this patch: 

Patches required with this patch: 

Obsoleted by: 

Files included with this patch:

/usr/bin/mkdir

Problem Description:

1237009 users umask modifies ACL's of new files under default ACL's
4073684 "mkdir -p dir" and "mkdir dir" work differently in the presence of default ACLs

Patch Installation Instructions: 
-------------------------------- 
Refer to the Install.info file within the patch for instructions on
using the generic 'installpatch' and 'backoutpatch' scripts provided
with each patch.  Any other special or non-generic installation
instructions should be described below.

Special Install Instructions: 
----------------------------- 

	NOTE:   To get the complete fix for 1237009 (users umask modifies
                ACL's of new files under default ACL's) and 4073684 (mkdir
                -p dir" and "mkdir dir" work differently in the presence
                of default ACLs), one should install 103640-19 (KU patch)
                or newer.

	As a result of this change, the setfacl man page.  Please refer
	to the following paragraph for details.

	****************************************************************
	A directory may contain default ACL entries.  If a  file  is
     	created  in  a  directory that contains default ACL entries,
     	the newly  created  file  will  have  permissions generated
     	according  to  the intersection  of the default ACL entries, 
     	and the permissions requested at creation time.  The umask(1) 
     	will not be applied if the directory contains default ACL
     	entries. if a  default  ACL is specified for a specific user 
     	(or users), the file will have a regular ACL  created;  
     	otherwise,  only the mode bits will be initialized according 
     	to the intersection described above.  The default ACL should 
     	be thought of as  the maximum discretionary access permissions 
     	that may be granted. 
	****************************************************************