From owner-freebsd-security@FreeBSD.ORG  Fri Nov 21 05:50:50 2008
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 66D251065670
	for <freebsd-security@freebsd.org>;
	Fri, 21 Nov 2008 05:50:50 +0000 (UTC)
	(envelope-from rea-fbsd@codelabs.ru)
Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45])
	by mx1.freebsd.org (Postfix) with ESMTP id 130BF8FC22
	for <freebsd-security@freebsd.org>;
	Fri, 21 Nov 2008 05:50:50 +0000 (UTC)
	(envelope-from rea-fbsd@codelabs.ru)
DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru;
	h=Received:Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender;
	b=FVxtaYSagpEuyg87dFe+qRexT/zLtBSN0pgIZzZCHDCbpklgG5I/cFdkmcqFSyrFQ4tf2WVEfJd//X3UusSVwpS2zI4bkOo44dMjKB/dGb0cVxeL0jjoasxNrh3NTiL+E0Sp0hQVsNN9VWA17+0R83e03vSSjIGerUvhsGmGwTA=;
Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25])
	by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256)
	id 1L3Oum-0003em-HY; Fri, 21 Nov 2008 08:50:48 +0300
Date: Fri, 21 Nov 2008 08:50:47 +0300
From: Eygene Ryabinkin <rea-fbsd@codelabs.ru>
To: freebsd-security@freebsd.org
Message-ID: <Nr4bFBjnW8SC2cBhy37/xqxP6SM@h3Iv+XGzMlVsqQhKLTPQUFtjrxk>
References: <6p2tlso0g3Xi5suHfErE3rcPs54@Mr6N54GlMnGhD+RQ1Yhx+24IxLk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="o7gdRJTuwFmWapyH"
Content-Disposition: inline
In-Reply-To: <6p2tlso0g3Xi5suHfErE3rcPs54@Mr6N54GlMnGhD+RQ1Yhx+24IxLk>
Sender: rea-fbsd@codelabs.ru
Cc: openssh@openssh.com
Subject: Re: Plaintext recovery attack in SSH, discovered by CPNI?
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Security issues \[members-only posting\]"
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2008 05:50:50 -0000


--o7gdRJTuwFmWapyH
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Me again.

Wed, Nov 19, 2008 at 04:20:58PM +0300, Eygene Ryabinkin wrote:
> Just came across the following list in the oss-security list:
>   http://www.cpni.gov.uk/Docs/Vulnerability_Advisory_SSH.txt

For you interest, CVE was created and it has some interesting
links inside (SANS one explains some general trends):
  http://cve.mitre.org/cgi-bin/cvename.cgi?name=3DCVE-2008-5161

It seems that some vendors are moving to the CTR encryption mode as the
default one.  Does anyone has something to say about this?  As I
understand, the advisory from CPNI is public, so there is no point to
refraining from discuissing this in the open lists.  OpenSSH people, I
understand that this is not just "two day business", but can you at
least drop a mail that you're investigating this?

Thanks a lot.
--=20
Eygene
 _                ___       _.--.   #
 \`.|\..----...-'`   `-._.-'_.-'`   #  Remember that it is hard
 /  ' `         ,       __.--'      #  to read the on-line manual  =20
 )/' _/     \   `-_,   /            #  while single-stepping the kernel.
 `-'" `"\_  ,_.-;_.-\_ ',  fsc/as   #
     _.-'_./   {_.'   ; /           #    -- FreeBSD Developers handbook=20
    {_.-``-'         {_/            #

--o7gdRJTuwFmWapyH
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkkmTDcACgkQthUKNsbL7Yib9ACeLXYHttvIidCKvsq4guYfBHTf
iYgAn1pw1j6x0kLrCxDqaUaFZDVNfL6K
=KujY
-----END PGP SIGNATURE-----

--o7gdRJTuwFmWapyH--