From owner-freebsd-security@FreeBSD.ORG  Mon Sep  9 12:51:32 2013
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
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 ESMTP id 30BA92A4
 for <freebsd-security@freebsd.org>; Mon,  9 Sep 2013 12:51:32 +0000 (UTC)
 (envelope-from feld@FreeBSD.org)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com
 [66.111.4.27])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id E23D02222
 for <freebsd-security@freebsd.org>; Mon,  9 Sep 2013 12:51:31 +0000 (UTC)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43])
 by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id CECD021D7A
 for <freebsd-security@freebsd.org>; Mon,  9 Sep 2013 08:51:19 -0400 (EDT)
Received: from web3 ([10.202.2.213])
 by compute3.internal (MEProxy); Mon, 09 Sep 2013 08:51:20 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=message-id:from:to:mime-version
 :content-transfer-encoding:content-type:in-reply-to:references
 :subject:date; s=smtpout; bh=reNXOmU5c8IrpbfltyWHH3/w0EU=; b=o/c
 mANzsiS7Bj+u3hGRg8sbD022ujA2yWG355iWRolE3E0csLcTujruj9+IidsscVSU
 I2U8QgW9HpHKjS2e3yEa+IG5oGr0tjiZM+4snGCisZX0JqxdP5PzEQpNmPBHJSXo
 0vBJRjHwfSCOb8UmA+bg7RhuVYvodVzyqsEZsdZE=
Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99)
 id 97D03B000AE; Mon,  9 Sep 2013 08:51:19 -0400 (EDT)
Message-Id: <1378731079.24879.19687157.0DBE99D1@webmail.messagingengine.com>
X-Sasl-Enc: BM6+NRW8qRF7lhbJM9z70Ai8Vg7sSXt49+B23+5yXdWm 1378731079
From: Mark Felder <feld@FreeBSD.org>
To: freebsd-security@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-15090c31
In-Reply-To: <20130909144142.J99094@sola.nimnet.asn.au>
References: <20130909144142.J99094@sola.nimnet.asn.au>
Subject: Re: Anything in this story of concern?
Date: Mon, 09 Sep 2013 07:51:19 -0500
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Mon, 09 Sep 2013 12:51:32 -0000

I'm still waiting for someone to thoroughly analyze this question

What's worse: the possibility that NSA has cracked RC4 or being
vulnerable to BEAST/CRIME?

Set your crypto to a minimum of TLS 1.1 and let everyone who can't
connect complain. At least their data wasn't compromised.

This entire situation is maddening.