Re: [Endymail] FW: Group/Enterprise encrypted email
Phillip Hallam-Baker <phill@hallambaker.com> Wed, 03 June 2015 21:09 UTC
Return-Path: <hallam@gmail.com>
X-Original-To: endymail@ietfa.amsl.com
Delivered-To: endymail@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 980541B2E62 for <endymail@ietfa.amsl.com>; Wed, 3 Jun 2015 14:09:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.123
X-Spam-Level:
X-Spam-Status: No, score=0.123 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 OF4g9183Vr86 for <endymail@ietfa.amsl.com>; Wed, 3 Jun 2015 14:09:53 -0700 (PDT)
Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E51631B2E61 for <endymail@ietf.org>; Wed, 3 Jun 2015 14:09:52 -0700 (PDT)
Received: by labpy14 with SMTP id py14so17978145lab.0 for <endymail@ietf.org>; Wed, 03 Jun 2015 14:09:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=NfzeD3Ezeykjp85EVDRkL+M6nUgcxT7gcuvxDRinWlE=; b=z8i+SzGneNC0VJpNXUGsyOiK2EiU69F9QnC1YtrUqKiLEguMbD4HCs65cIXaXihZr0 a47dn3XYvgR878YYkTWIbtXTmUWpuTDylyBR5kBh8MipX89IREnrimhYd6NwOMTgYrEt khBZvnX2+Z8kQGbO0NPZ4Rdhn/1BRIQ3w0ybdqf1BxwC+GwuhwyLlskUGbGZ3YO1JXIq KTDZtEMGW+rbWPypm2FTnTqh7at9vPoboYbd1RfO55NESjYmW88mbA2Gb7FR2ySeHqam UoKdS2FIGvcGsaVQQ4MRLtkpWpe/JBHvNRdADWXHMB3vzQAE4kwc5iXx2yxL4K2TLAZl f/dw==
MIME-Version: 1.0
X-Received: by 10.112.126.42 with SMTP id mv10mr27815843lbb.58.1433365791470; Wed, 03 Jun 2015 14:09:51 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.203.163 with HTTP; Wed, 3 Jun 2015 14:09:51 -0700 (PDT)
In-Reply-To: <82E7C9A01FD0764CACDD35D10F5DFB6E7E159E@001FSN2MPN1-046.001f.mgd2.msft.net>
References: <82E7C9A01FD0764CACDD35D10F5DFB6E7DFBBD@001FSN2MPN1-046.001f.mgd2.msft.net> <000d01d09cef$76039f10$620add30$@icloud.com> <82E7C9A01FD0764CACDD35D10F5DFB6E7E1094@001FSN2MPN1-046.001f.mgd2.msft.net> <007001d09e27$3c3083f0$b4918bd0$@icloud.com> <82E7C9A01FD0764CACDD35D10F5DFB6E7E154A@001FSN2MPN1-046.001f.mgd2.msft.net> <CAMm+Lwgk9pMdURgNg=vvSbwNkQw_Q9Qmn=bgExU7Mqdvsun_DA@mail.gmail.com> <82E7C9A01FD0764CACDD35D10F5DFB6E7E159E@001FSN2MPN1-046.001f.mgd2.msft.net>
Date: Wed, 03 Jun 2015 17:09:51 -0400
X-Google-Sender-Auth: 9yYQ6KTq5HyvItwV0EBgIu-WZhU
Message-ID: <CAMm+Lwikmt--GVVT_UPYjY5WcxcBJ_2geg5EkA47F7=gp-sYww@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: "Nordgren, Bryce L -FS" <bnordgren@fs.fed.us>
Content-Type: multipart/alternative; boundary="001a11c36bc6d579f10517a37a28"
Archived-At: <http://mailarchive.ietf.org/arch/msg/endymail/6FV6sKUxVZ4i4nFCeujf0jlXfm4>
Cc: Trevor Freeman <trevor.freeman99@icloud.com>, "endymail@ietf.org" <endymail@ietf.org>
Subject: Re: [Endymail] FW: Group/Enterprise encrypted email
X-BeenThere: endymail@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <endymail.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/endymail>, <mailto:endymail-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/endymail/>
List-Post: <mailto:endymail@ietf.org>
List-Help: <mailto:endymail-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/endymail>, <mailto:endymail-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2015 21:09:54 -0000
On Wed, Jun 3, 2015 at 4:45 PM, Nordgren, Bryce L -FS <bnordgren@fs.fed.us> wrote: > > In a corporate context, this makes perfect sense. If I am downloading > company confidential > > material to my laptop, I want to be able to read it on the laptop but I > don't want to accidentally > > send a copy to someone else by doing an unfortunate 'reply all'. > > So another thing to note in security considerations is that this is a > scheme intended to protect well behaved actors who have good habits and an > honest software ecosystem from causing damage due to specific single honest > mistakes. It is not intended to protect against adversaries, well behaved > actors who have sloppy habits, well behaved actors who make more than one > mistake on the same message (reply all + attachment with no > tag/inappropriate tag), or well behaved actors who make a single mistake > from which multiple correlated incorrect actions are derived (misclassify > content -> incorrect content tag/incorrect mailing list). > > In light of these things, I think any language about "ensuring that policy > is followed" or the like should just be expunged. If the target is to > encourage well-meaning partners to do the accepted thing, that's how it > should be presented. As I said to a former director of the NSA recently, the fact that Snowden and Manning had effectively unrestricted access to such a large amount of data is an indictment of both the institution and the approach to controlling information. The classification level of a document is a measure of the ego of the author/classifier, not how important it is to keep it secret. If keeping documents secret causes operational difficulties, people will not attach the security labels necessary to control them properly. Trying to absolutely control the flow of information has a lousy track record. And not just in the US but FOIA means that the US examples are rather more obvious. Trying to lock everything down resulted in security systems so complicated, even an MIT professor was unable to figure them out when he was made CIA director. The lesson we have learned is that imperfect security systems that are acceptable to end users are much more effective than theoretically perfect schemes that users bypass. It is possible that the US federal govt. will learn the same lesson someday. If they ever do, they know where to look.
- [Endymail] FW: Group/Enterprise encrypted email Nordgren, Bryce L -FS
- Re: [Endymail] [kitten] Group/Enterprise encrypte… Nordgren, Bryce L -FS
- Re: [Endymail] FW: Group/Enterprise encrypted ema… Trevor Freeman
- Re: [Endymail] FW: Group/Enterprise encrypted ema… Nordgren, Bryce L -FS
- Re: [Endymail] FW: Group/Enterprise encrypted ema… Trevor Freeman
- Re: [Endymail] FW: Group/Enterprise encrypted ema… Nordgren, Bryce L -FS
- Re: [Endymail] FW: Group/Enterprise encrypted ema… Phillip Hallam-Baker
- Re: [Endymail] FW: Group/Enterprise encrypted ema… Nordgren, Bryce L -FS
- Re: [Endymail] FW: Group/Enterprise encrypted ema… Phillip Hallam-Baker
- Re: [Endymail] FW: Group/Enterprise encrypted ema… Nordgren, Bryce L -FS
- Re: [Endymail] FW: Group/Enterprise encrypted ema… Trevor Freeman