From owner-freebsd-security@FreeBSD.ORG Tue Apr 8 18:00:09 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 786C38FC for ; Tue, 8 Apr 2014 18:00:09 +0000 (UTC) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 41A2A1D8B for ; Tue, 8 Apr 2014 18:00:09 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a] (saphire3.sentex.ca [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a]) by smarthost1.sentex.ca (8.14.8/8.14.8) with ESMTP id s38I059F068432 for ; Tue, 8 Apr 2014 14:00:05 -0400 (EDT) (envelope-from mike@sentex.net) Message-ID: <53443917.7040609@sentex.net> Date: Tue, 08 Apr 2014 13:59:51 -0400 From: Mike Tancsa Organization: Sentex Communications User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: freebsd-security@freebsd.org Subject: Re: FreeBSD's heartbleed response References: <20140408174210.GA5433@behemoth> In-Reply-To: <20140408174210.GA5433@behemoth> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.74 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: Tue, 08 Apr 2014 18:00:09 -0000 On 4/8/2014 1:42 PM, Chris Nehren wrote: > later, FreeBSD remains unpatched. There are many worried > sysadmins and other users in #freebsd and elsewhere wondering > what's going on and when their systems will be patched. So far > all we have is an unofficial gist on github and some discussion > here (which most users don't see) with no further information. > More transparency is needed. * The port was very quickly updated. * Xin posted a working patch to the list for those who really wanted to apply it. * I think it reasonable that code touching such a CRITICAL aspect of the OS be *well* reviewed before getting committed. IIRC there was a quick fix to an openssl bug in the past that then had to be fixed again. * What is stopping people who care about security from joining, or following this mailing list ? ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/