Re: [lamps] S/MIME fix

Phillip Hallam-Baker <phill@hallambaker.com> Thu, 17 May 2018 15:46 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2732F12EB9E for <spasm@ietfa.amsl.com>; Thu, 17 May 2018 08:46:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level:
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 cP1lE6bkR6xJ for <spasm@ietfa.amsl.com>; Thu, 17 May 2018 08:46:25 -0700 (PDT)
Received: from mail-ot0-x231.google.com (mail-ot0-x231.google.com [IPv6:2607:f8b0:4003:c0f::231]) (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 2C5E512EB95 for <SPASM@ietf.org>; Thu, 17 May 2018 08:46:23 -0700 (PDT)
Received: by mail-ot0-x231.google.com with SMTP id n3-v6so5571866ota.5 for <SPASM@ietf.org>; Thu, 17 May 2018 08:46:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=C+9/B+hM5Rje4Edo0R23Rf8zfodz4/0V2fPg4DeNlzA=; b=jHPrJT5mVo9sjOTNuHY1iVUXIzreidt8taXylm1W3Cdn/A5xvEppcO3eBwW1+vJQaD oxezitSJieTuFnEukx8SG4AOfh1MW6rTP26MOpO7YKViB6pdWOLZZeRLKGfAvUW/bjA9 Q+v2Dim8gtwxA/lgcOlF8Qgr2ME7W45dExECSjo2mdikmkpRsbMSXvRo2iOiCADSwZ8p uVwwegSLZ2uwj9d30Zf2ExFFTojn54mW33we3ZZvuIs/IPHN2t4oj4ZwTPwrgfqTmHLe MtmDwANMmBJvifXf0o8otXxnnmmfygdSgBzoZzOlmM+EU7YQ8iK8s6RTBLtvGk6p7Z6D RbgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=C+9/B+hM5Rje4Edo0R23Rf8zfodz4/0V2fPg4DeNlzA=; b=AiVQaLT/+e3p9cpgovK5QjlIOn6x204S10CUpaKsSKaDeAsgEq2AR/5vstEgn9wy+D WSB7qTuTLkDvFt+ycJHgNsv5720UO1wN4F1KPxz75UFCSPZVlWcmOGaTIiNkwZkutI4w MpxkEyXvReX4S54zaEqeO0R0CQhQrhECD7PgYUr/2AxJXUgA44L+G6xhNXIC84t1K8CI 29nUTzNOeTXKxYckr7yILFrDwWQ5xun1BK6lHh6Xth94JGFjgzWFdnLY+VUixraB2XK4 xFuKUsj+f506ndBFhd7BGSvi5Qug4nFyW8qvwrsf1MCn6zhmQlP7TJeMU90llpn2PnvJ ovug==
X-Gm-Message-State: ALKqPwermsga6mcKbEVke4MWNZGNlWxkyqjzsw4WzIJD5pzzNNhjqQKN 38MDfBNK9vRqSNzkwhh3f/iJCzMi92z6eeWztlw=
X-Google-Smtp-Source: AB8JxZpV3uQ0q2L4XHhyCIHEtt/uTLc4ne+OnwDBdnsSdRp4a3y43wC46yB1fnS02jMtxSxhzzXYLlcdBF4epn9P1lw=
X-Received: by 2002:a9d:14b9:: with SMTP id d54-v6mr4156162ote.380.1526571982385; Thu, 17 May 2018 08:46:22 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 2002:a9d:23:0:0:0:0:0 with HTTP; Thu, 17 May 2018 08:46:21 -0700 (PDT)
In-Reply-To: <f623981f-a379-4a94-0fda-a765a8318841@nostrum.com>
References: <CAMm+Lwj=VTBHYxH-iOaqEUHxALpBfSXWG3p0+xxUnY+o4CmGvA@mail.gmail.com> <BN6PR14MB1106A2890EE8B9243B4EA08C83920@BN6PR14MB1106.namprd14.prod.outlook.com> <CAMm+LwhuBoQ1VHQy-=E2FODYq4Fnzs8e24Yqyfg4akwQTsqc=w@mail.gmail.com> <1e8468d7-da6c-62f1-e24b-1ee03df22606@cs.tcd.ie> <e678276f-79c2-ec3c-7df5-f70794740f77@nostrum.com> <AB332E06-E1F5-4E82-9EF8-B49846865DAC@vigilsec.com> <f623981f-a379-4a94-0fda-a765a8318841@nostrum.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 17 May 2018 11:46:21 -0400
X-Google-Sender-Auth: ZNPbI22ANiQFw8i_b-HXYrq5mqY
Message-ID: <CAMm+LwjFqv4JiRLTBAcZB+EvBC0nH53jgBaCfFfaGTa5QSbrZw@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: Russ Housley <housley@vigilsec.com>, SPASM <SPASM@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bbf898056c68bcdc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/AualAwr40f9Bs0DBrf8VLwqySPk>
Subject: Re: [lamps] S/MIME fix
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2018 15:46:33 -0000

On Thu, May 17, 2018 at 11:37 AM, Adam Roach <adam@nostrum.com> wrote:

> On 5/17/18 9:01 AM, Russ Housley wrote:
>
>> To create an analogous situation for secure email, you'd need to use
>>> webcrypto in a way that stored your private key in the browser
>>> (inaccessible to the page), and develop web standards that add some
>>> affordance for web pages to hand encrypted data to the browser in a way
>>> that causes the corresponding unencrypted data to be displayed to the user,
>>> but isolated from the web page completely (e.g., rendered into an iframe
>>> that the parent cannot inspect).
>>>
>> I am not following you.  I do not see the requirement to do anything with
>> webcrypto.  However, I completely agree with the need to isolate each
>> portion of the multi-part.
>>
>
> Presumably, we would need a means to generate a keypair, and to make the
> public key available to the webpage so that it can be conveyed to remote
> parties. That could be a new API, but it feels like something that could be
> added to webcrypto without much fuss. (I'll note that WebRTC did take the
> other approach, by defining an RTCPeerConnection.generateCertificate()
> method that is very roughly equivalent to window.crypto.subtle.generateKey(),
> but with the properties I describe above).
>
> Admittedly, this can all be done by the browser itself using local UI, but
> the general idea of the web platform is that you delegate only as little as
> is necessary to the browser. I mean, if you push enough of this to the
> local binary, and it becomes a full-fledged email client. ;)


​That was the CERN approach.

Netscape disagreed, threw JavaScript together in a fortnight and launched
it on the world with no consultation. We have been in damage control ever
since.

A modern Web browser is a Turing complete language for constructing thick
clients for the Web Services of your choice. I don't like the fact but it
is what it is.

I am composing this in Gmail right now. And there is my outlook client in
the window underneath. ​The Web browser is not just a full fledged email
client, it is the client of choice.