Re: [Uta] Opportunistic encryption and authentication agility

Watson Ladd <watsonbladd@gmail.com> Tue, 25 March 2014 23:11 UTC

Return-Path: <watsonbladd@gmail.com>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9AB31A027B for <uta@ietfa.amsl.com>; Tue, 25 Mar 2014 16:11:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 QCLMJwprQ2Lp for <uta@ietfa.amsl.com>; Tue, 25 Mar 2014 16:11:30 -0700 (PDT)
Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 2E49E1A0256 for <uta@ietf.org>; Tue, 25 Mar 2014 16:11:30 -0700 (PDT)
Received: by mail-yh0-f53.google.com with SMTP id v1so1325050yhn.40 for <uta@ietf.org>; Tue, 25 Mar 2014 16:11:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=8NUm/8TXIwzdXUSxYvxgWiE5gcvbRbFt8wW51C6epIE=; b=cX8GjAHM05f5S40/33L467wZ7Q06bB1jGKi5O0zq3UCDy9Hw+oocLaiDNchTO9LURS TKYJUsyWFTT6lEpdlkdK18ak00s3DfALVY9vsXFMxw+1DSQpVQ+/O39cjgnWB2eEhxGs 6jizBAOlMmCI9hdYkX6eES8sdHQgLDieHjXNTgWT3RsLFe9Xh8ABmzDtiyFQg8x32FRZ athj0mErkuaKf2bptRrEi11StIjQmEf8/WnSqgW8K425U1koozDBVzbMZR7TMstG2jVz xZyaAO5E6s6UGO43gRpOIoHGqYow2n2Qrus4uiwTYUdsQCo3i5oGr9xwbcAI8aT7V4no 8CvQ==
MIME-Version: 1.0
X-Received: by 10.236.163.73 with SMTP id z49mr69696552yhk.43.1395789088781; Tue, 25 Mar 2014 16:11:28 -0700 (PDT)
Received: by 10.170.80.214 with HTTP; Tue, 25 Mar 2014 16:11:28 -0700 (PDT)
In-Reply-To: <CAGZ8ZG0nyfNvpkL2e39Or0W8WVeDXjdcCzPQE-DNjaY2t+j-sw@mail.gmail.com>
References: <CAGZ8ZG0rBxiE2dGZXhpvhKiyJOu=6Bn8sQ2seJ9_KvgPjmaaRg@mail.gmail.com> <532CFAB0.4070301@network-heretics.com> <10492.1395613933@sandelman.ca> <533042FF.7060603@network-heretics.com> <53305B5D.8030708@fifthhorseman.net> <53305EFD.9030003@network-heretics.com> <53306294.4070205@fifthhorseman.net> <CAGZ8ZG2GYTYfrSDGxEMS3eRsg2g_LaWP_pyHt9vmz4NV2cGAEw@mail.gmail.com> <CAA4WUYhffWpsxU1FrmQ1np1EObaC5EgMC-R7QDj8C0ODTRLPdQ@mail.gmail.com> <CAGZ8ZG0nyfNvpkL2e39Or0W8WVeDXjdcCzPQE-DNjaY2t+j-sw@mail.gmail.com>
Date: Tue, 25 Mar 2014 19:11:28 -0400
Message-ID: <CACsn0cnwtxTpYyNK71wi99Vq=8wJQDY8c1ye_19H+py-wD-a1g@mail.gmail.com>
From: Watson Ladd <watsonbladd@gmail.com>
To: Trevor Perrin <trevp@trevp.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/uta/QBu-5xenPbqAr45xXUx0ubqVJF4
Cc: "uta@ietf.org" <uta@ietf.org>, "William Chan (陈智昌)" <willchan@chromium.org>
Subject: Re: [Uta] Opportunistic encryption and authentication agility
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Mar 2014 23:11:37 -0000

On Tue, Mar 25, 2014 at 4:47 PM, Trevor Perrin <trevp@trevp.net> wrote:
> On Tue, Mar 25, 2014 at 1:24 PM, William Chan (陈智昌)
> <willchan@chromium.org> wrote:
>> On Tue, Mar 25, 2014 at 1:09 PM, Trevor Perrin <trevp@trevp.net> wrote:
>>>
>>> On Mon, Mar 24, 2014 at 9:51 AM, Daniel Kahn Gillmor
>>> <dkg@fifthhorseman.net> wrote:
>>> > On 03/24/2014 12:36 PM, Keith Moore wrote:
>>> >
>>> >> So, what's the incentive for either clients or servers to support OE if
>>> >> clients just silently accept it without any indication to the user?
>>> >> Just for the good of mankind?
>>> >
>>> > I'd say "to increase the cost of pervasive monitoring" and "to resist
>>> > surveillance by passive attackers"
>>>
>>> I'd go further - OE for HTTP could have strong auth added to it in the
>>> future, such as pinning or DANE, which *could* be indicated to the
>>> user.
>>
>>
>> Please be cautious about suggesting user indications. UI is complicated and
>> all that. More specifically in the browser case, even if you could strongly
>> authenticate a connection over which you request a http:// page, I wouldn't
>> want to give that page the https lock treatment. Note that https:// has
>> different semantics (referer semantics, mixed content, etc).
>
> Good points, thanks.  Maybe adding other auth methods to HTTP-over-TLS
> would be best done silently, with no UI unless a security failure
> occurs?

Sadly this doesn't work. If I can imitate the website because of a
WebPKI failure, I can pretend to not support whatever additional auth
is done. It's the reason OCSP stapling doesn't work.

Furthermore, taking an economic perspective, authentication has a
winner-take-all aspect to it. A new client has to support the
authentication everyone already uses. But a site only has to support
the authentication the client accepts. Any new authentication
mechanism will only be adopted in domains where the existing one
doesn't work.

Sincerely,
Watson Ladd
>
> I think I like that, as I think catching "badness" is more useful than
> indicating "goodness".  But these are hard Qs, I'm just trying point
> out some possibilities at this point.
>
>
> Trevor
>
> _______________________________________________
> Uta mailing list
> Uta@ietf.org
> https://www.ietf.org/mailman/listinfo/uta



-- 
"Those who would give up Essential Liberty to purchase a little
Temporary Safety deserve neither  Liberty nor Safety."
-- Benjamin Franklin