IETF Logo Mail Archive

Re: [perpass] "Guide to intranet protection"?

Albert Lunde <atlunde@panix.com> Thu, 28 November 2013 15:25 UTC

Return-Path: <atlunde@panix.com>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 917F31AE120 for <perpass@ietfa.amsl.com>; Thu, 28 Nov 2013 07:25:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.802
X-Spam-Level:
X-Spam-Status: No, score=-2.802 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FBC33KLnNhvo for <perpass@ietfa.amsl.com>; Thu, 28 Nov 2013 07:25:35 -0800 (PST)
Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) by ietfa.amsl.com (Postfix) with ESMTP id A54BB1AD7BF for <perpass@ietf.org>; Thu, 28 Nov 2013 07:25:35 -0800 (PST)
Received: from [192.168.15.3] (unknown [50.9.9.201]) by mailbackend.panix.com (Postfix) with ESMTP id 4B0F135D9C for <perpass@ietf.org>; Thu, 28 Nov 2013 10:25:34 -0500 (EST)
Message-ID: <5297607B.3070103@panix.com>
Date: Thu, 28 Nov 2013 09:25:47 -0600
From: Albert Lunde <atlunde@panix.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: perpass <perpass@ietf.org>
References: <5295FC4F.7060309@dcrocker.net> <5295FDE8.5000402@cs.tcd.ie> <m2mwkpgpi0.wl%randy@psg.com> <5296C8CC.2060508@dcrocker.net> <027a01ceebfb$df99f290$9ecdd7b0$@huitema.net> <m2d2llgisa.wl%randy@psg.com> <CAMm+LwgEoi8o1Uc4H9sB8L7SY=XtYQYBQQD0RMXONLQXKecvEA@mail.gmail.com>
In-Reply-To: <CAMm+LwgEoi8o1Uc4H9sB8L7SY=XtYQYBQQD0RMXONLQXKecvEA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [perpass] "Guide to intranet protection"?
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2013 15:25:37 -0000

Loosely on topic, there is this recent blog entry from Twitter on what 
they did to implement Forward Security:

https://blog.twitter.com/2013/forward-secrecy-at-twitter-0

The main point seems to be that they dynamically rotate through SSL 
session keys and try to avoid storing them anywhere long-term.

They in turn cite:

Imperial Violet "How to botch TLS forward secrecy"

https://www.imperialviolet.org/2013/06/27/botchingpfs.html

v2.23.0 | Report a Bug | By Email