From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 69BA5138A1F for ; Thu, 10 Apr 2014 10:50:00 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3B2C3E0A53; Thu, 10 Apr 2014 10:49:52 +0000 (UTC) Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1C7C4E09DA for ; Thu, 10 Apr 2014 10:49:50 +0000 (UTC) Received: by mail-pd0-f177.google.com with SMTP id y10so3719289pdj.36 for ; Thu, 10 Apr 2014 03:49:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=4YG2Dg8dvPLaMO6qnpWb2AFGs+bsJWNO6+3nNjphJ3Q=; b=PC2cYOebHZjgAIZ/Ns+Tqt6lk+f4Vj4E/YdqAGHRjdBT1i9UT3Elhjey9Obfixb4x0 ksXOgiwOrkafsAXQVxbHydfzT+uqIups2yTmvrxDTHANNU3gTXdK7bvL5dzrXnOmeKm4 VtwotROjPvv692gu+xfgSDps1WFzEppc6C7zqZqeQnBpczJ72xHWUyoqx9jHTIcaXKEQ AlokdcdQDvQgdqoLftnbiSIZlw/Oc0v69el62aFYEOue3Q2h64wAczcftFXG4Rk2b3CK 7tw2/OqWrn/hC7nsYP4s0tDDRM0gt0uezArFZAhUIetCdD8UiMtp/vLqv53xr49mA3lZ Zrtg== X-Received: by 10.66.164.201 with SMTP id ys9mr18945816pab.40.1397126989840; Thu, 10 Apr 2014 03:49:49 -0700 (PDT) Received: from localhost (exit-01a.noisetor.net. [173.254.216.66]) by mx.google.com with ESMTPSA id y4sm8253901pbk.76.2014.04.10.03.49.45 for (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 10 Apr 2014 03:49:48 -0700 (PDT) Date: Thu, 10 Apr 2014 10:52:21 +0000 From: Matthew Finkel To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] 'Heartbleed' bug Message-ID: <20140410105216.GA27859@localhost> References: <20140410000635.GB9729@syscon7.ed.shawcable.net> <5345E6A2.2030400@gentoo.org> <53466A28.6000609@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <53466A28.6000609@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: 90064047-00fd-480c-b5ee-5d95d290301e X-Archives-Hash: d613fdc265ce80ac7f3cad2727c8085f On Thu, Apr 10, 2014 at 05:53:44PM +0800, J?n Zahornadsk? wrote: > On 04/10/2014 05:03 PM, Adam Carter wrote: > > > > What surprises me here is OpenSSH. It's not supposed to use OpenSSL > > but Debian update process suggests to restart it after updating > > OpenSSL to a fixed version. Is it an overkill on their part? It > > might confuse admins. > > > > > > adam@proxy ~ $ ldd /usr/sbin/sshd > > linux-vdso.so.1 (0x00007fffb068e000) > > libwrap.so.0 => /lib64/libwrap.so.0 (0x00007f68db1e6000) > > libpam.so.0 => /lib64/libpam.so.0 (0x00007f68dafd8000) > > libcrypto.so.1.0.0 => /usr/lib64/libcrypto.so.1.0.0 (0x00007f68dabf5000) > > libutil.so.1 => /lib64/libutil.so.1 (0x00007f68da9f2000) > > libz.so.1 => /lib64/libz.so.1 (0x00007f68da7db000) > > libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f68da5a4000) > > libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f68da387000) > > libc.so.6 => /lib64/libc.so.6 (0x00007f68d9fd7000) > > libgcc_s.so.1 => > > /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/libgcc_s.so.1 (0x00007f68d9dc0000) > > libdl.so.2 => /lib64/libdl.so.2 (0x00007f68d9bbc000) > > /lib64/ld-linux-x86-64.so.2 (0x00007f68db3f1000) > > adam@proxy ~ $ qfile /usr/lib64/libcrypto.so.1.0.0 > > dev-libs/openssl (/usr/lib64/libcrypto.so.1.0.0) > > adam@proxy ~ $ > > > > So OpenSSH clearly IS using OpenSSL, and you need to restart sshd after > > upgrading OpenSSL. > > As far as I know, it doesn't use it for the communication itself, just > some key generations, so it shouldn't be affected by this bug. But I > guess better safe than sorry... > Right. heartbleed does not directly affect openssh, but openssh uses openssl and it's good practice to keep the shared libraries on-disk and the shared libraries in-memory in sync.