Re: [Endymail] FW: Group/Enterprise encrypted email
Phillip Hallam-Baker <phill@hallambaker.com> Wed, 03 June 2015 20:08 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 8462D1A6EE0 for <endymail@ietfa.amsl.com>; Wed, 3 Jun 2015 13:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 F0mkQQ9KIEu4 for <endymail@ietfa.amsl.com>; Wed, 3 Jun 2015 13:08:02 -0700 (PDT)
Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) (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 01B021A90B3 for <endymail@ietf.org>; Wed, 3 Jun 2015 13:08:01 -0700 (PDT)
Received: by labko7 with SMTP id ko7so16847717lab.2 for <endymail@ietf.org>; Wed, 03 Jun 2015 13:07:59 -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=QgR1SppmSk89pJcd4q9EHpb+/4eaQMUXXm9jxjzpmX8=; b=GSpvJYWV55mYyYJNPclEv7KqbbsOu9SI0+Jle0BqfGcbWIm0pPd/IXPWFa7cKsW5WK cRsqJfGa3vlaoCbtf8oNE0zq8rQOJZjShJh2Sqft8JnjjJbQNG8XPQFSAOcxEhbWflSd h0QJoKtUrqn2/esdv5+vHTpEtVUTvpvBlcCTXTOpfPyyse5KehnkKA3DTyZt04YK8wHT zwD71lsaXGp/APn5LoHT95nV6Bqig+EZdp+Kdm0iq6LjdRzICsP2Fh1reSQD2bCLYKJA Z1tcMQCYQZ5keUcNlhc7/RfODKWN77VpHyL0PnrsA74YSxbWTXwzqpOIHc/22uNfvWOL S9zQ==
MIME-Version: 1.0
X-Received: by 10.112.166.5 with SMTP id zc5mr19303830lbb.91.1433362079454; Wed, 03 Jun 2015 13:07:59 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.203.163 with HTTP; Wed, 3 Jun 2015 13:07:59 -0700 (PDT)
In-Reply-To: <82E7C9A01FD0764CACDD35D10F5DFB6E7E154A@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>
Date: Wed, 03 Jun 2015 16:07:59 -0400
X-Google-Sender-Auth: DHGDukry1nH_v4Uw-UFA1B5U3ps
Message-ID: <CAMm+Lwgk9pMdURgNg=vvSbwNkQw_Q9Qmn=bgExU7Mqdvsun_DA@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: "Nordgren, Bryce L -FS" <bnordgren@fs.fed.us>
Content-Type: multipart/alternative; boundary="001a11c26906949e950517a29d72"
Archived-At: <http://mailarchive.ietf.org/arch/msg/endymail/h_B_-E-pH-3qSlcW-hQYlzmk1GY>
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 20:08:03 -0000
On Wed, Jun 3, 2015 at 3:49 PM, Nordgren, Bryce L -FS <bnordgren@fs.fed.us> wrote: > > I'm having a hard time wrapping my head around the notion of enforcement > comingling with "no obligations on receipt" of the key. Enforcement is an > obligation. Trevor sais 'no Technical obligations'. I think what he means here is that people who use this technology are probably going to use clients that make a best effort to not leak confidential bits but not require the use of trustworthy hardware that can provide technical enforcement. In other words, I can use a completely open source client modified in any way I like without having to get the executable signed by someone the rights owner trusts. 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'.
- [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