Re: [saag] The Mathematical Mesh

Ben Laurie <benl@google.com> Wed, 24 April 2019 18:01 UTC

Return-Path: <benl@google.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE2A112017D for <saag@ietfa.amsl.com>; Wed, 24 Apr 2019 11:01:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.5
X-Spam-Level:
X-Spam-Status: No, score=-17.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 JQoDZtY3Pf45 for <saag@ietfa.amsl.com>; Wed, 24 Apr 2019 11:01:43 -0700 (PDT)
Received: from mail-yb1-xb2e.google.com (mail-yb1-xb2e.google.com [IPv6:2607:f8b0:4864:20::b2e]) (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 82C16120118 for <saag@ietf.org>; Wed, 24 Apr 2019 11:01:43 -0700 (PDT)
Received: by mail-yb1-xb2e.google.com with SMTP id p134so7461172ybc.4 for <saag@ietf.org>; Wed, 24 Apr 2019 11:01:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=phI0EIwQpAAsAqI+wyYi90h9Pb/udQGPegsf0KeZrQ0=; b=QS6RvMx+EIreyX9Hzs5Ak/K4NTlMtLJrHN2HP61yo5hHIPOs8aE7PlAHJMF+q75YQp DtzM/fnNF9kwlX2UdldFZ1KG9bQ6bFya0tJe1nuVXbAtG2YsT9+QMc+fKud6PB1vLGr1 +EwjEJnjE90f35qWggMGFfpmchBgN/vcu9CrU8BW3fYvgpa6dERiu7AWQxMPpSkIulFq KPZ647tncDKKLptPRmGesAt7iSJSOES855TbQ1SNPH3UDBdd8O3cElb+cl7z0SQXIZ7W +Xu8hsf0awtWjDRz1xOZuG9HTHHyLcs1Tl45/w2EJ9+V0oKeZmiAE5y9jIhDNXNgC6ik 0Tfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=phI0EIwQpAAsAqI+wyYi90h9Pb/udQGPegsf0KeZrQ0=; b=TnzyDqNZQEc0F+EC11+g9fJqnllU7ztV7GoRlGsvcwZKKND/SZq7orb8+l59qBvDJA wJTMGyvZICFEz6qlMIk9p0iQqzLA1/yYd3BYlmrfmNtxgW1qaAJJ0sdjaeeYgMmpbD+2 kalQVFKvP4Tr1Axwlwg74ALcW7Tzpx2mLKwSPfkkBUB/nJcHK/VG4x85xDRwLqS0pIqc 3vooJnjRI5uddD+0Dngchm+nUhGjKJLqw5juhuU+MJmivvwpjWR1nCO395Ltg+1NQxkF sz1qldocKjbpjIRBXdd2h+V4aAYnv+ECKw0za8nvC7e3movNqCJ35bykS714SuuG7sRL Ht0g==
X-Gm-Message-State: APjAAAVprTdMJuoFHAYFgqXHVC/430oh36MOgqhJsvAOfkTfYMGFzHFw X2NI0nDl82YCg50a7A5VY3HjgS3GQjLisJ+syM4m6Q==
X-Google-Smtp-Source: APXvYqyoeJtO8TQvWStR5jsDWHQDbpEk0adahyKDBUstkk5Cr61TURUzhHQhvZ+CYcs2tm41eyPNNmASHwLq6PhFY68=
X-Received: by 2002:a25:b317:: with SMTP id l23mr3125809ybj.513.1556128902404; Wed, 24 Apr 2019 11:01:42 -0700 (PDT)
MIME-Version: 1.0
References: <CAMm+LwiF3iGiRO5reW4KCgf8vp=Kv=+4pD+_rGOcxEsD1Hxk4g@mail.gmail.com> <20190422190302.GA3137@localhost> <CAMm+Lwj1BV1=UQwE8-5tPO_mxOVixfkiUjXvu+U_AgnSzzkjvg@mail.gmail.com> <CABrd9STVA=fT+oH7f4S_x8JQVaQRUJASWCY5g4pnhQL6ezWaHA@mail.gmail.com> <CAMm+LwhEGTCG7Ucu7xiv0fYZHjxAhe5D6MdU6EYN4UTi0zLnrg@mail.gmail.com> <CAG5KPzwr9oAP5270jE2N-Sw=d_g_YuhQ5_qB3W0OfggGrcU_qA@mail.gmail.com> <CAMm+LwgCBAXqWspkgjGdUX-zUwEf7EtBCe8oiHYF2eoJMpR=Ng@mail.gmail.com> <CAG5KPzxC09HFmR4YaGPPxZRene_ix=XWs02JVoWmiDRTSybvWA@mail.gmail.com> <CAMm+Lwjp9Ybn3TWp0xppEFXmD4mZB6RAs6cXvBpsSx5HxWPd+A@mail.gmail.com>
In-Reply-To: <CAMm+Lwjp9Ybn3TWp0xppEFXmD4mZB6RAs6cXvBpsSx5HxWPd+A@mail.gmail.com>
From: Ben Laurie <benl@google.com>
Date: Wed, 24 Apr 2019 19:01:28 +0100
Message-ID: <CABrd9STTKHT4k_aB2UX0ke+B6bfFBXNm4pcv8q4aiT=o1TJW-A@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: Ben Laurie <ben@links.org>, secdispatch@ietf.org, IETF SAAG <saag@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000074533805874a7ea5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/KJH4zZKvaJaXmAwOFt7LWLyRM8Y>
Subject: Re: [saag] The Mathematical Mesh
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2019 18:01:46 -0000

On Wed, 24 Apr 2019 at 18:49, Phillip Hallam-Baker <phill@hallambaker.com>
wrote:

>
> The reason that the World Wide Web exists at all is that Tim Berners-Lee
> ignored the sage advice of the hypertext community that referential
> transparency was essential and pressed ahead with 'scruffy links'. Nobody
> did usability testing to decide whether the gopher or Web UI was the
> approach to follow until long after we knew the answer.
>

This is a clear case of survivorship bias. The users did the usability
testing. WWW survived (despite being technically terrible in many ways),
the competitors did not.



> My criticism of usability testing is this: we do not find out if buildings
> will stay up by building them and seeing if they fall down. That is exactly
> how it was done in the past which is why the Bent Pyramid collapsed during
> construction.
>
> Usability testing is the scientific approach. We should have moved past
> science and started practicing engineering. We should be able to predict
> with some confidence how users will react by applying principles learned
> from individual tests.
>

Indeed, somewhat possible.

Some classes of usability failure are quite easy to analyze. If a user
> faces two potential situations, case A and case B where one will lead to
> disaster and the other will perform the intended task and has no means of
> distinguishing these cases, the product is defective.
>
> Right now, I have no means of knowing if an email from my bank is actually
> an email from my bank or not. And that should be considered a problem. The
> problem I have with discussions of usability is that the argument is made
> that because we might not be able to serve every user we should just give
> up and never try to change anything.
>

Well, the problem I have with discussions of usability is the argument is
made that we should leave that until all the tech is figured out, or that
we don't need to bother because the thing is obviously better. Going from
.1% to 1% is clearly an improvement, but it is not a solution.

BTW, my original question was not about QR codes (though I have my doubts
about those), but about this assertion about usability: "Otherwise, there
are many existing protocols that make comparison of 15-30 character base 32
encoded strings as the basis for mutual authentication and these have
proved effective and acceptable."


-- 
I am hiring! Formal methods, UX, management, SWE ... verified s/w and h/w.
#VerifyAllTheThings.

*https://grow.googleplex.com/jobs/search?query=team:%221944651479079%22
<https://grow.googleplex.com/jobs/search?query=team:%221944651479079%22>*