Re: [perpass] Violating end-to-end principle: I-D Action: draft-farrelll-mpls-opportunistic-encrypt-00.txt

"Christian Huitema" <huitema@huitema.net> Fri, 17 January 2014 06:23 UTC

Return-Path: <huitema@huitema.net>
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 A33631ADF85 for <perpass@ietfa.amsl.com>; Thu, 16 Jan 2014 22:23:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.3
X-Spam-Level:
X-Spam-Status: No, score=-3.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_NONE=-0.0001] 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 FGZAlBKMReUB for <perpass@ietfa.amsl.com>; Thu, 16 Jan 2014 22:23:05 -0800 (PST)
Received: from xsmtp04.mail2web.com (xsmtp24.mail2web.com [168.144.250.190]) by ietfa.amsl.com (Postfix) with ESMTP id 389BC1ADF76 for <perpass@ietf.org>; Thu, 16 Jan 2014 22:23:05 -0800 (PST)
Received: from [10.5.2.15] (helo=xmail05.myhosting.com) by xsmtp04.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1W42pP-0000PR-Fl for perpass@ietf.org; Fri, 17 Jan 2014 01:22:52 -0500
Received: (qmail 31898 invoked from network); 17 Jan 2014 06:22:50 -0000
Received: from unknown (HELO HUITEMA5) (Authenticated-user:_huitema@huitema.net@[24.16.156.113]) (envelope-sender <huitema@huitema.net>) by xmail05.myhosting.com (qmail-ldap-1.03) with ESMTPA for <adrian@olddog.co.uk>; 17 Jan 2014 06:22:50 -0000
From: Christian Huitema <huitema@huitema.net>
To: 'Phillip Hallam-Baker' <hallam@gmail.com>, 'Theodore Ts'o' <tytso@mit.edu>
References: <04c001cf1123$7e5c00c0$7b140240$@olddog.co.uk> <CAMm+Lwj0r3PNoBC0Y1ydibD3piioZ57Z1Ks-Ea6o58xahjXKwQ@mail.gmail.com> <20140116192320.GD32098@thunk.org> <CAMm+Lwh9306PBjUR7iSUqQYEZNNQswxLZ92ri3D3fOpmWe8SzQ@mail.gmail.com>
In-Reply-To: <CAMm+Lwh9306PBjUR7iSUqQYEZNNQswxLZ92ri3D3fOpmWe8SzQ@mail.gmail.com>
Date: Thu, 16 Jan 2014 22:22:47 -0800
Message-ID: <021301cf134c$8bcc54a0$a364fde0$@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQF0Acy8YdaXXCAmfcgNFLBaLQGzOQKyuo5sAtdBCbYCc0fKFZr+qV1Q
Content-Language: en-us
Cc: 'Adrian Farrel' <adrian@olddog.co.uk>, 'perpass' <perpass@ietf.org>, 'Stephen Kent' <kent@bbn.com>
Subject: Re: [perpass] Violating end-to-end principle: I-D Action: draft-farrelll-mpls-opportunistic-encrypt-00.txt
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: Fri, 17 Jan 2014 06:23:07 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> PGP and S/MIME are both unable to protect meta-data against an attacker with intercept capability.  
>
> STARTTLS is unable to protect content against attack by a corrupt system administrator.
>
> To have comprehensive security we need both the End 2 End security to protect the data at rest
> and the transport layer security to protect the metadata in motion.

Well, yes, of course. But we also have to start somewhere. STARTTLS is reasonably easy to deploy, and many mail services are either already deploying it or are in the process of deploying it. The channel protection with STARTTLS will not protect against compromised servers, and will not prevent providers to comply with national security letters and other subpoenas. But it will prevent the bulk collection of message headers by tapping links, and that's a very good first step.

- -- Christian Huitema
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (MingW32)
Comment: Using gpg4o v3.2.34.4474 - http://www.gpg4o.de/
Charset: utf-8

iQEcBAEBAgAGBQJS2Mw2AAoJELba05IUOHVQdHwH/RSjp+nR91GMvR9pOOh+axwg
Nyaw7EN6EXjsNyY22Ai2Zg993kBCdva4GXiIbmbTJjdpdjO76KLYJWQli7V78+Et
ZvrHHVedv0HAU9VthpYcKhfFcbNjnxy8pDWvFOF/UszQUXFk8QB8bZLLndHXBEEP
HggaKjVVda5/jCq/jMRIDVk8HyToIUwJaeWysv/U56T56rYiMkXOhnaRQXVYJJ1F
SS1tq29M0LKi7+copWNZjBO7keIfnbESs3k3Fc8GPJSW3F8+WoPZlbXGF4SAZFdw
bhtNQ8PKjAqMOmnoyP/NC0SZZY/Ck0vP40SV891AeTMwY3g6now2YXUzob6poRw=
=doiO
-----END PGP SIGNATURE-----