[Bimi] Fwd: Problematic cert activities

Wei Chuang <weihaw@google.com> Mon, 01 April 2019 16:10 UTC

Return-Path: <weihaw@google.com>
X-Original-To: bimi@ietfa.amsl.com
Delivered-To: bimi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98B181202C6 for <bimi@ietfa.amsl.com>; Mon, 1 Apr 2019 09:10:33 -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 yKyO9DNB_BNg for <bimi@ietfa.amsl.com>; Mon, 1 Apr 2019 09:10:30 -0700 (PDT)
Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) (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 414AF1202BB for <bimi@ietf.org>; Mon, 1 Apr 2019 09:10:30 -0700 (PDT)
Received: by mail-vs1-xe32.google.com with SMTP id d8so4826658vsp.2 for <bimi@ietf.org>; Mon, 01 Apr 2019 09:10:30 -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; bh=EMnDDJ8zWFm76WPNbpRpFuZAXjkjWOp9pnztJW3Nii4=; b=f8Yn+pU56yMDJ4t1s1QBn//uIXKok670UHpCXECPDajneWN/UPYbgTpqPhOEJF3ojQ ILuzuy7CvPyg/a0gSaYHVhkdOBRWxQE+L86IAMQxlRtdVeKP2UCDZIouQmMwDuP2ETpG d5w9Yi5m3/N2Je0pUbRUbdUhsqrCjXBVz3A6qDWbRSMfPl+5+oakJx2R7xW+ceLySwUR TOILzhXyXh7Bl0xxJxE8Ngnc4M0TnbsyLCsmwyGJxdm3qj5v/ncsU7rVAd3o8S9nrwfQ s5b4hYIBNVm6B0gFTwCIieAZZtWi2/wPi6CqPerU+vmMzqp4UJePXU2GdGXt8Aq2ChYw DsYw==
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; bh=EMnDDJ8zWFm76WPNbpRpFuZAXjkjWOp9pnztJW3Nii4=; b=j1OyrVHYSehiOoKkHm/JMUi1FMayBbi/yqe+1SlN/CCoq1Gj2pEGgSB13EVEp6u+B7 E7RIk+thLn7R+fmJX9g8TQ5MSyo216kM69pATXnP+GdnVmzG8k8xF7HloX9o96zQTgUD yWT06rcKJyvqlTIZlQ6KaAY5Xspc3XCYs/ZgKExMCCCzK4LAicGDwK0B8QI5/uF+4d52 k7MYrU7kAaMY3AXgWJ0uWIhZRLf/EYudX7DUd0+/QKJCgAjTrBJEgTZ241mCtvjoFICc Xn3xrxdy2dJGo9QmtnZzY96Jn5tDfw3GJ9wgpse9R77OAb9gCenYEDCfK/dDDZVHwEeu EbwA==
X-Gm-Message-State: APjAAAV+YzWq2QHRisqnbz6l/3Yk0eew6QIVhwl6JSSyNhQhmkjb0zoI 5bwq7tZSuNdg1Nb2Gc5gAXrt1LQqjCv944fZD68swNDBbv0=
X-Google-Smtp-Source: APXvYqzk8oVoNkAucS7j5QSs39Zv0MQrJbHRg+QD40sZ03BtZ5gmxUIhdnf5rFajNFV6bO+L/a72+FrCGGJj0M9GFxE=
X-Received: by 2002:a67:e30a:: with SMTP id j10mr15622114vsf.103.1554135026895; Mon, 01 Apr 2019 09:10:26 -0700 (PDT)
MIME-Version: 1.0
References: <6e99b975-73d8-9f57-450f-bfa1c2227a31@dcrocker.net> <CAAFsWK3OPmS6Wz5bFqHnDFgH8Za5PgjYer5qg6wd3BAS_sdYWw@mail.gmail.com> <5cd60888-b690-2cde-2156-5ed145394a01@bbiw.net>
In-Reply-To: <5cd60888-b690-2cde-2156-5ed145394a01@bbiw.net>
From: Wei Chuang <weihaw@google.com>
Date: Mon, 01 Apr 2019 09:10:13 -0700
Message-ID: <CAAFsWK2oaW39bpBhxQJHzJM2hUA_2gv6bY=11TMkLX3_-MeiTg@mail.gmail.com>
To: bimi@ietf.org
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="00000000000040242105857a42dd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bimi/qoA94SJJA_7Hq7Xh6t6vMBNY_VY>
Subject: [Bimi] Fwd: Problematic cert activities
X-BeenThere: bimi@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Brand Indicators for Message Identification <bimi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bimi>, <mailto:bimi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bimi/>
List-Post: <mailto:bimi@ietf.org>
List-Help: <mailto:bimi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bimi>, <mailto:bimi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Apr 2019 16:10:34 -0000

---------- Forwarded message ---------
*From: *Dave Crocker <dcrocker@bbiw.net>
*Date: *Sun, Mar 31, 2019 at 4:33 PM
*Subject: *Re: [Bimi] Problematic cert activities
*To: *Wei Chuang <weihaw@google.com>


On 3/31/2019 4:18 PM, Wei Chuang wrote:
> With regards to VMC, in theory there's a face-to-face validation step to
> could mitigate this though that is only done on the initial request.
> I'll have to check if subsequent certificate requests are vulnerable or
> if other measures protect against this type of attack.


In an unrelated, and relatively random conversation today, I had a bit
of insight that is no doubt obvious to serious security folk but hadn't
occurred to me:  We have the concept of 2FA, with two independent
channels that provide validation of the requestor. But we ought to add
the idea of two-factor confirmation.  So rather than just sending an
email to confirm that the owner of the cited email address agrees with
whatever the transaction is, do a second, separation confirmation -- eg,
via the phone number.

The set of attack behaviors described by Bill are such that I doubt this
would have made a difference -- there were more basic holes being
exploited -- but I suspect there is value to be had with it.

The broader point is that we seem not to take a holistic approach to
protection of infrastructure services...


> PS Sorry for the delay in getting back to this as I was in transit.

Delay?  There was a delay? ...


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net