GNU bug report logs - #8391
chmod setuid & setguid bits

Previous Next

Package: coreutils;

Reported by: Christian <chris <at> computersalat.de>

Date: Thu, 31 Mar 2011 16:48:04 UTC

Severity: normal

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

Full log

Message #92 received at 8391 <at> debbugs.gnu.org (full text, mbox):

From: Bob Proulx <bob <at> proulx.com>
To: Bruno Haible <bruno <at> clisp.org>
Cc: chris <at> computersalat.de, bug-gnulib <at> gnu.org, ovasik <at> redhat.com,
	8391 <at> debbugs.gnu.org
Subject: Re: bug#8391: chmod setuid & setguid bits
Date: Mon, 5 Mar 2012 13:38:54 -0700

Bruno Haible wrote:
> It's because this use of '+' is easy to remember.
> "chmod +x" means "add execution permissions".
> "chmod -x" means "remove execution permissions".

To be pedantic that isn't quite true.  To be pedantic it actually is
gated by the process umask in effect at that time.  You need the 'a'
or other target in order to avoid the umask layer.

  "chmod +x" means "add execution permissions qualified by umask".
  "chmod -x" means "remove execution permissions qualified by umask".

  "chmod a+x" means "add execution permissions".
  "chmod a-x" means "remove execution permissions".

Bob
This bug report was last modified 13 years and 80 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.