public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Miloslav Trmac <mitr@redhat.com>
To: Cody Maloney <cmaloney@theoreticalchaos.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH v2 3/4] chsh: Add libuser support
Date: Mon, 28 Jan 2013 17:01:30 -0500 (EST)	[thread overview]
Message-ID: <1221077942.16839972.1359410490623.JavaMail.root@redhat.com> (raw)
In-Reply-To: <CA+K3q6qDgdrXxbesZ-373xMYgA=oyjMnaejJWNtBaYj8HfR04w@mail.gmail.com>

Hello,
----- Original Message -----
> On Mon, Jan 14, 2013 at 10:16 AM, Miloslav Trmac <mitr@redhat.com>
> wrote:
> > (On second thought, if the program is setuid, the setuid execution
> > mechanism doesn't change supplementary groups, so perhaps the call
> > isn't strictly necessary; Still, initializing the groups makes the
> > environment more deterministic.  And as long as initgroups() is
> > called, it should be called in a way that works.)
> 
> I'm fine with/would prefer dropping the initgroups entirely (That the
> initgroups man page, at least on my system, specifically talks about
> reading them from /etc/group, never mentioning nss worries me). If
> that's okay with you, otherwise I can move it to the beginning of
> dropping privileges.

Sorry about the late reply; after discussing it with colleagues, it seems that dropping the initgroups() is completely safe here.
    Mirek

  reply	other threads:[~2013-01-28 22:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-13  9:12 [PATCH v2 0/4] Add support for using libuser to chsh and chfn Cody Maloney
2013-01-03  3:21 ` [PATCH 0/3] Add support for using libuser to chsh Cody Maloney
2013-01-03  3:21   ` [PATCH 1/3] chsh-chfn: Add flag for enabling/disabling libuser support Cody Maloney
2013-01-03  3:22   ` [PATCH 2/3] chsh: Move pam auth to its own function Cody Maloney
2013-01-03  3:22   ` [PATCH 3/3] chsh: Add libuser support Cody Maloney
2013-01-03 16:34     ` Miloslav Trmac
2013-01-07 11:51       ` Karel Zak
2013-01-08  6:15         ` Cody Maloney
2013-01-08  6:17         ` Cody Maloney
2013-01-08  6:18         ` Cody Maloney
2013-01-13  9:12   ` [PATCH 2/3] chsh: Move pam auth to its own function Cody Maloney
2013-01-13  9:12 ` [PATCH v2 1/4] chsh-chfn: Add flag for enabling/disabling libuser support Cody Maloney
2013-01-13  9:12 ` [PATCH v2 2/4] chsh-chfn: Move pam auth to its own function, factoring out common code Cody Maloney
2013-01-13  9:12 ` [PATCH v2 3/4] chsh: Add libuser support Cody Maloney
2013-01-14 18:16   ` Miloslav Trmac
2013-01-17  0:52     ` Cody Maloney
2013-01-28 22:01       ` Miloslav Trmac [this message]
2013-01-13  9:12 ` [PATCH v2 4/4] chfn: " Cody Maloney
     [not found] ` <50F2FBBE.7000305@gmail.com>
2013-01-13 19:31   ` [PATCH v2 0/4] Add support for using libuser to chsh and chfn Cody Maloney

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

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

  git send-email \
    --in-reply-to=1221077942.16839972.1359410490623.JavaMail.root@redhat.com \
    --to=mitr@redhat.com \
    --cc=cmaloney@theoreticalchaos.com \
    --cc=util-linux@vger.kernel.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