X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org X-Authority-Analysis: v=1.0 c=1 a=xe8BsctaAAAA:8 a=r3BWHh_mkfot7XfJoEYA:9 a=l8t8j7GRG_c64-fJQUEA:7 a=APpgQe5SzfEE-9V1lpX02e6KdsIA:4 a=eDFNAWYWrCwA:10 a=rPt6xJ-oxjAA:10 Message-ID: <47F2D593.6010106@byu.net> Date: Tue, 01 Apr 2008 18:38:43 -0600 From: Eric Blake User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080213 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Building perl-5.10.0 References: <7634A226C4C245868140309A0F3A952F AT desktop2> <2kap83p6s5819lu66sr6kmrem6o5iqm180 AT 4ax DOT com> <56E5E10621694E4A860212458ECD1E1C AT desktop2> <015b01c7bf20$a3d3e4a0$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <9ea6aaa80803172015i3adb46cq3af80a70fa7ff063 AT mail DOT gmail DOT com> <47E5384E DOT 3070503 AT x-ray DOT at> <47E711BE DOT 2020608 AT byu DOT net> <20080401132111 DOT GR4468 AT calimero DOT vinschen DOT de> <20080401134424 DOT GS4468 AT calimero DOT vinschen DOT de> In-Reply-To: <20080401134424.GS4468@calimero.vinschen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Corinna Vinschen on 4/1/2008 7:44 AM: | Erm... hang on. I just tested this on Linux: | | | This looks like what we do on Cygwin, too. Then we're in good company :) In other words, no need to go changing things to be different than Linux, until we've proven Linux is wrong. | Shouldn't the "nobody" entry | disappear when calling chmod? That's how I understand the statement in | the POSIX docs: | | "An alternate file access control mechanism shall [...] be disabled for | a file after the file permission bits are changed for that file with | chmod( ). The disabling of the alternate mechanism need not disable | any additional mechanisms supported by an implementation." | | Either the ACLs of a file are not an "alternate" access mechanism, | but an "additional" access mechanism. But that doesn't match the | description either: | | "An additional access control mechanism shall only further restrict | the access permissions defined by the file permission bits." Yes, those were the two paragraphs I was noticing when I made my claim that cygwin's chmod(2) wasn't obeying POSIX. ACLs can serve as both "alternate" (give more rights to some users than what is implied by the traditional stat bits) and "additional" (restrict rights to certain users outside of what is shown in the traditional stat bits). | | Or, Linux doesn't follow POSIX here, which seems unlikely to me. Actually, it seems highly likely to me - after all, at one point, POSIX considered standardizing a form of ACLs, but it never went anywhere (and in the meantime, several competing styles of how to implement ACLs cropped up; Solaris and Linux tackle the issue noticably different, and Selinux security descriptors are yet another wrinkle in the picture). Maybe it's worth asking on the Austin Group mailing list? | | Or, I completly misunderstand what the above quote means. No, your understanding matched mine. - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9 AT byu DOT net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkfy1ZMACgkQ84KuGfSFAYCpOwCeN/av36V08YCmkTTSDnVBO5EX tU0An1gVK7kRaGrZSJDxX8SFr/WSD1vx =opK3 -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/