From: Peter Seebach <peter.seebach@windriver.com>
To: "Peter A. Bigot" <pab@pabigot.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] prevent pseudo host passwd/group contamination
Date: Mon, 3 Nov 2014 12:55:22 -0600 [thread overview]
Message-ID: <20141103125522.623ba486@e6410-2> (raw)
In-Reply-To: <1414861479-5493-1-git-send-email-pab@pabigot.com>
On Sat, 1 Nov 2014 12:04:36 -0500
"Peter A. Bigot" <pab@pabigot.com> wrote:
> The new patches use --without-passwd-fallback, preventing contamination
> from the host files during the early build stages when the target
> versions from base-passwd aren't yet available.
I like these, and will see whether I can free up time to work on this. If I
can't, though, I have no objections to these (and the previous set) being
added to oe-core as local patches until next time I have a free day or two to
study the password code.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
next prev parent reply other threads:[~2014-11-03 18:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-01 17:04 [PATCH 0/3] prevent pseudo host passwd/group contamination Peter A. Bigot
2014-11-01 17:04 ` [PATCH 1/3] pseudo: default --without-passwd-fallback Peter A. Bigot
2014-11-14 16:16 ` Burton, Ross
2014-11-14 16:47 ` Peter A. Bigot
2014-11-14 17:08 ` Peter A. Bigot
2014-11-14 17:34 ` Burton, Ross
2014-11-15 16:20 ` Peter A. Bigot
2014-11-01 17:04 ` [PATCH 2/3] pseudo: provide fallback passwd and group files Peter A. Bigot
2014-11-12 7:36 ` zhangxiao
2014-11-12 11:15 ` Peter A. Bigot
2014-11-13 2:31 ` zhangxiao
2014-11-13 3:04 ` Peter A. Bigot
2014-11-13 3:28 ` zhangxiao
2014-11-01 17:04 ` [PATCH 3/3] bitbake.conf: pseudo fall back to last-resort passwd files Peter A. Bigot
2014-11-03 18:55 ` Peter Seebach [this message]
2014-11-03 23:16 ` [PATCH 0/3] prevent pseudo host passwd/group contamination Burton, Ross
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=20141103125522.623ba486@e6410-2 \
--to=peter.seebach@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pab@pabigot.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.