From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: CoreOS vulnerability inherited from Gentoo?
Date: Thu, 2 Jun 2016 16:21:39 +0000 (UTC) [thread overview]
Message-ID: <loom.20160602T181634-587@post.gmane.org> (raw)
In-Reply-To: 1464877889.3249948.625957281.651B2BA7@webmail.messagingengine.com
Max R.D. Parmer <maxp <at> trystero.is> writes:
> > Which file contains the purported malaised default configration?
> > I just want to manually inspect it and verify for myself.
> /etc/pam.d/system-auth which is provided by pambase:
> https://gitweb.gentoo.org/proj/pambase.git/
Huh. I looked at that and concluded it could not possibly be the problem.
I went a bit deeper at coreOS and found that they are using
pambase-20101024 from 2010. Double_huh. I had heard they were behind
on updating may ebuilds, but that is ridiculous. Here are the details
should anyone be interested::
https://github.com/coreos/coreos-overlay/commit/
048faeb3b1b1a693dec3bdb47b127b8d71c48c13
I (previously) had high regards for CoreOS, but not keeping things current
is usually the largest source of problems and sploits, imho.
thx,
James
prev parent reply other threads:[~2016-06-02 16:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 16:30 [gentoo-user] CoreOS vulnerability inherited from Gentoo? James
2016-05-31 17:44 ` Mick
2016-05-31 17:59 ` Michael Cook
2016-05-31 18:44 ` [gentoo-user] " James
2016-05-31 18:07 ` [gentoo-user] " Max R.D. Parmer
2016-05-31 21:02 ` Max R.D. Parmer
2016-06-01 7:11 ` Neil Bothwick
2016-06-02 13:44 ` [gentoo-user] " James
2016-06-02 14:31 ` Max R.D. Parmer
2016-06-02 16:21 ` James [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20160602T181634-587@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.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