--- Begin Message ---
Subject: |
[Bug 62558] New - chmod g=o clears setgid bit |
Date: |
Tue, 2 Apr 2002 11:08:17 -0500 |
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug
report.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=62558
--- shadow/62558 Tue Apr 2 11:08:17 2002
+++ shadow/62558.tmp.11128 Tue Apr 2 11:08:17 2002
@@ -0,0 +1,49 @@
+Bug#: 62558
+Product: Red Hat Linux
+Version: 7.1
+Platform: All
+OS/Version: Linux
+Status: NEW
+Resolution:
+Severity: low
+Priority: normal
+Component: fileutils
+AssignedTo: address@hidden
+ReportedBy: address@hidden
+QAContact: address@hidden
+URL:
+Summary: chmod g=o clears setgid bit
+
+From Bugzilla Helper:
+User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020311
+
+Description of problem:
+chmod = operator uses all four bits from {u,g,o} when modifying permissions,
+whereas it should probably operate only on the rwx bits, and not the
+setuid/setgid/sticky bits, since these don't have commensurable meanings
+(certainly not for sticky, and arguably for setuid/setgid).
+
+Version-Release number of selected component (if applicable):
+chmod (GNU fileutils) 4.0.36
+
+How reproducible:
+Always
+
+Steps to Reproduce:
+1. mkdir /tmp/foo.d
+2. chmod 2775 /tmp/foo.d
+3. chmod g=o /tmp/foo.d
+4. ls -ld /tmp/foo.d
+
+
+Actual Results: drwxr-xr-x 2 dupuy sysman 1024 Apr 2 11:14
/tmp/foo.d
+
+Expected Results: drwxr-sr-x 2 dupuy sysman 1024 Apr 2 11:14
+/tmp/foo.d
+
+Additional info:
+
+Not sure what, if anything, POSIX.2 specifies about the behavior of chmod g=o.
+If they require this pretty stupid and unexpected behavior, I guess you have to
+implement it as such. It's quite possible they have nothing to say on the
+subject, though, since g=o type operations may be an extension of the POSIX.2
spec.
--- End Message ---