On Sat, 17 May 2008, Byron wrote:
> It's something of a "lesser of two evils" situation. In the absence of
> evidence either way, the only habit that would be worse is assuming that
> any distribution is not affected, simply because they do not publicly state
> that they are. Having said that, it's good to know that apparently Gentoo
> is not impacted.
- when a vulnerability has been found inside the package, the package is
vulnerable, it's not claimed to be distro-specific, and by default you
are right in assuming that every distro is affected.
- when a vulnerability has been found in a *distro-specific* patch or
script (or ebuild (or Windows-specific version ) ), the vulnerability is
claimed to reside in the distro scripts, or in the distro patch. So it's
each linux distribution can not handle every other-distro-specific
vulnerability. Gentoo has sometimes gentoo-specific vulnerabilities
, and Debian too. Debian does not issue any statement that they are
not affected by a Gentoo-specific vulnerability. No distro does that.
And there would be a lot of other distributions to monitor ... That
would really be a mess.
"In Debian Security Advisory 1571, the Debian Security Team disclosed a
weakness in the random number generator used by OpenSSL on Debian and its
"OpenSSL 0.9.8c-1 up to versions before 0.9.8g-9 on Debian-based
If you are unsure about your provider advisory, go and see the original
and official advisories (Debian, Mitre CVE) which are very clear. Then
revoke your contract and change of provider :)
Futhermore, a public RSA weak key (because being created by a vulnerable
Debian openssl) that would have been uploaded to
gentoo:~foo/.ssh/authorized_keys on a Gentoo system would make this
Gentoo system vulnerable to a trivial remote compromise as soon as the
attacker knows the "foo" user login. We can't simply say "be confident,
you are safe because you are using Gentoo". That would be lying. It
depends on your configuration and consequently that's the responsibility
of the root. There are a lot of similar configuration or user-land
risks, and that's not the purpose of the vulnerability monitoring that
is provided by the GLSA process.
By the way, the firstname.lastname@example.org mailing list is obviously the
right place to publicly inform that Gentoo openssl package is not
vulnerable to CVE-2008-0166. Now that's done, thanks to Peter who
firstly asked for it.
Raphael Marichez aka Falco
Gentoo Linux Security Team