bug-coreutils@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: "Pádraig Brady" <P@draigBrady.com>
To: 10311-done@debbugs.gnu.org
Subject: bug#10311: RFE: Give chmod a "-h" option as well
Date: Wed, 20 Mar 2024 19:16:00 +0000	[thread overview]
Message-ID: <aed5dedb-f9e4-2a5a-4a42-90d1e296362a@draigBrady.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1112161721430.6649@frira.zrqbmnf.qr>

On 16/12/2011 16:29, Jan Engelhardt wrote:
> Hi,
> 
> chown(1) has a -h option by which it affects symlinks directly rather
> than the pointed-to file. The bonus side effect is that the
> pointed-to files don't get changed in any way, which is kinda welcome
> if you attempt to "fix" permissions/ownership in a directory where an
> evil user could create a symlink to e.g. /etc/shadow.
> 
> Attempting chmod -R g+w /home/groups/evilgroup is still a risk, and
> would necessity a more long-winded command involving find(1). It
> would therefore be welcome that chmod receive an -h option that just
> skips over them (besides perhaps attempting to change their
> permissions as well).

Pushed at
https://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=v9.4-162-g07a69fc3b

Marking as done.

cheers,
Pádraig.




      parent reply	other threads:[~2024-03-20 19:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16 16:29 bug#10311: RFE: Give chmod a "-h" option as well Jan Engelhardt
2011-12-16 17:30 ` Bob Proulx
2011-12-16 17:42   ` Eric Blake
2011-12-16 18:37     ` Bob Proulx
2011-12-16 18:58       ` Paul Eggert
2011-12-16 19:04       ` Eric Blake
2011-12-16 20:16         ` Eric Blake
2011-12-16 17:59   ` Jan Engelhardt
2011-12-16 18:24     ` Bob Proulx
2011-12-16 18:06   ` Paul Eggert
2024-03-20 19:16 ` Pádraig Brady [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/bug-coreutils

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aed5dedb-f9e4-2a5a-4a42-90d1e296362a@draigBrady.com \
    --to=p@draigbrady.com \
    --cc=10311-done@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).