public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] CoreOS vulnerability inherited from Gentoo?
Date: Wed, 1 Jun 2016 08:11:19 +0100	[thread overview]
Message-ID: <20160601081119.7f7c5480@digimed.co.uk> (raw)
In-Reply-To: <3181100.83d2K62WRd@dell_xps>

[-- Attachment #1: Type: text/plain, Size: 940 bytes --]

On Tue, 31 May 2016 18:44:10 +0100, Mick wrote:

> > The operator user was not used by CoreOS, but existed because it
> > exists in the Gentoo Portage system from which CoreOS is derived.
> > <end/snippets>
> > 
> > Full read [1]. It kinda shows that CoreOS is derived from Gentoo
> > and not ChromeOS; at least when time to blame a security lapse
> > elsewhere....

ChromeOS is based on Gentoo, so if CoreOS is based no ChromeOS it is a
second generation Gentoo derivative.

> Does this mean we need to do anything to improve the security of our
> systems?

The report seems to be saying that the problem is caused by using the
Gentoo default config, which assumes a Gentoo environment. So  it's fine
on Gentoo. But it won't hurt to run glsa-check from time to time (my sync
script does it every time and mails me if there's a problem).


-- 
Neil Bothwick

Everything else being equal, fat people use more soap.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2016-06-01  7:11 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 [this message]
2016-06-02 13:44     ` [gentoo-user] " James
2016-06-02 14:31       ` Max R.D. Parmer
2016-06-02 16:21         ` James

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=20160601081119.7f7c5480@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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