From owner-freebsd-security@FreeBSD.ORG Thu Apr 10 10:10:22 2014 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1A9E0BC2 for ; Thu, 10 Apr 2014 10:10:22 +0000 (UTC) Received: from mail.carlostrub.ch (319.ch [88.198.108.251]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CDF291D75 for ; Thu, 10 Apr 2014 10:10:20 +0000 (UTC) Received: from c-st.net (localhost [127.0.0.1]) (Authenticated sender: cs@carlostrub.ch) by mail.carlostrub.ch (Postfix) with ESMTPA id 6738B18CC29; Thu, 10 Apr 2014 12:10:10 +0200 (CEST) Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: FreeBSD Security Advisory FreeBSD-SA-14:06.openssl X-Powered-BY: OTRS - Open Ticket Request System (http://otrs.org/) X-Mailer: OTRS Mail Service (3.3.5) Date: Thu, 10 Apr 2014 12:10:09 +0200 Message-ID: <1397124609.974780.949873937.113568.2@c-st.net> To: Lena@lena.kiev.ua Organization: Carlo Strub From: Carlo Strub In-Reply-To: <20140409084809.GA2661@lena.kiev> References: <20140409084809.GA2661@lena.kiev> <201404082334.s38NYDxr098590@freefall.freebsd.org> <201404090821.s398LMg7020616@mech-cluster241.men.bris.ac.uk> Cc: freebsd-security@freebsd.org, mexas@bris.ac.uk X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2014 10:10:22 -0000 >=20 > SSH is not affected. >=20 SSH is indeed not affected, but I guess you should still consider the secre= t sshd key on your otherwise affected server as burnt, as it might have bee= n in the memory too while an attacker was inspecting it via heartbleed. Bet= ter recreate the secret ssh key and all other secret keys on your server as= well. But, again, the OpenSSH protocol/software per se are not affected.=