Re: [perpass] Getting started...

Randy Bush <randy@psg.com> Sat, 17 August 2013 15:58 UTC

Return-Path: <randy@psg.com>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBA0911E8190 for <perpass@ietfa.amsl.com>; Sat, 17 Aug 2013 08:58:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level:
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id puPlPbTZY32O for <perpass@ietfa.amsl.com>; Sat, 17 Aug 2013 08:58:23 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 3220F11E818A for <perpass@ietf.org>; Sat, 17 Aug 2013 08:58:23 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VAitM-0000Zj-EE; Sat, 17 Aug 2013 15:58:16 +0000
Date: Sun, 18 Aug 2013 00:58:14 +0900
Message-ID: <m2siy8e2cp.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "Russ White" <russw@riw.us>
In-Reply-To: <022e01ce9b5c$3c471130$b4d53390$@riw.us>
References: <520E5684.1090005@cs.tcd.ie> <6.2.5.6.2.20130816171144.0c01f738@resistor.net> <520F4AE1.5040403@cs.tcd.ie> <m27gfkfwmm.wl%randy@psg.com> <520F525C.5020800@cs.tcd.ie> <022e01ce9b5c$3c471130$b4d53390$@riw.us>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: perpass@ietf.org, 'Stephen Farrell' <stephen.farrell@cs.tcd.ie>
Subject: Re: [perpass] Getting started...
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "The perpass list is for discussion of the privacy properties of IETF protocols and concrete ways in which those could be improved. " <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: Sat, 17 Aug 2013 15:58:23 -0000

> Why not focus on providing proxies and the like to obfuscate the
> traffic path rather than trying to encrypt the routing table?

if it's cheap, do both.  every cm we can raise the bar cheaply is a win

>>> i would love it if my email client ( well, normal email clients :-)
>>> automagically encrypted to the recipients for whom i have a public key.
>>> maybe the folk way up there at layer seven can come up with an even
>>> better idea.
> Thunderbird+Enigmail does this.

yep.  trying to move family members and coworkers to that mode.  but, as
i hinted, i use a horribly irregular emacs-based email client.

> I know lots of folks with public keys, but they won't encrypt their
> email traffic, because "I have nothing to hide" --and complete bit of
> nonsense, but very prevelant.

i am hoping the frogs will notice the rising water temperature.  foolish
of me, probably.  but this is one reason why i suggested privacy by
default.