lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120521142643.GA28118@burratino>
Date:	Mon, 21 May 2012 09:27:00 -0500
From:	Jonathan Nieder <jrnieder@...il.com>
To:	richard -rw- weinberger <richard.weinberger@...il.com>
Cc:	Ben Hutchings <ben@...adent.org.uk>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org, stable@...r.kernel.org, lwn@....net
Subject: Re: Linux 3.2.18

Hi Richard,

richard -rw- weinberger wrote:
> On Mon, May 21, 2012 at 4:02 PM, Ben Hutchings <ben@...adent.org.uk> wrote:

>> All users of the 3.2 kernel series should upgrade.
>
> Should or must?

Every stable update probably includes some fixes that are
security-relevant for someone.  That said, no one on this list has
volunteered to do the nontrivial work of categorizing them (and that
is not the purpose of this list anyway).  You're more likely to find
useful information from your distributor or from sources such as the
national vulnerability database.

Amazingly enough, the difference between "should" and "must" is not a
secret message but just a difference in diction between Ben and Greg.

"All users should upgrade" would generally mean that it is prudent for
all users to upgrade, rather than some particular subset of them
(e.g., users who have been experiencing build failures).

Kind regards,
Jonathan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ