[Trans] Mozilla's basic take on Binary Transparency

Richard Barnes <rlb@ipv.sx> Tue, 28 March 2017 19:21 UTC

Return-Path: <rlb@ipv.sx>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C148129A05 for <trans@ietfa.amsl.com>; Tue, 28 Mar 2017 12:21:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20150623.gappssmtp.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 xiEQp4h_naRw for <trans@ietfa.amsl.com>; Tue, 28 Mar 2017 12:21:40 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 E7A0A129A09 for <trans@ietf.org>; Tue, 28 Mar 2017 12:21:39 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id o81so6525347wmb.1 for <trans@ietf.org>; Tue, 28 Mar 2017 12:21:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=PHs8OKCgH13rRPATYbXLmI1UFPfU0YMsI6E8QxhZK64=; b=Yi4QZo0dUphyQPUB09TmE+oIUVIp4X3Kuupw5dX+6ReMY/bSmqgJfHNKlQ9wEMb3YZ vMAlNwo8u7Hwaiim4qHtJhV1YrJ+Hala0Sx6sPgGhgsbutIzyp4NGVtTbDg8D70pprnD g35gjnTfft5cMSS4iysArbJ1ijcSTQ6xQc8cGD7+a2A+3nut8qD9RnXsyKQPgZXizj0q HMEJlpqmmVb7I1Hk87uA98zGdUZ/CP+A7QCpzADJjvXuPnksZ1C7Uv+4eatRB6nOEVNl uqpzBifiTjJX3j50ou7kBbmo+icvyKQYvwoZLEHNQXhibp+Dw/8kivxY0BR/WLdC3Jl4 6naw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=PHs8OKCgH13rRPATYbXLmI1UFPfU0YMsI6E8QxhZK64=; b=Y+k30BPoAGTW7xC9OE5VOWliw7Jgb5dsLMhzB0SxYof1haKhetXSGicLKfvIgVmcRN W7n82ltcnBuVInxbks00NTfh9po6upK9oMm+Vs/CPtS8z2h/kP+eoWDMayRGiHko9cxz D8VyO0Yz0iT3nIFsy999n4bYDUyR3EnQdoUS/9b70rhcL93asdV2Mg9/6LTFU/RDQ4eK H+wLnZ1ZxZiROnv8my5l6wMJtp1HulZ187lxnXXSdZpdeOe9286TXII4rVwGrnv2eXoZ Rldb+8chjylWzSlhwp7Mve2N/uhYcFxk3RJHZMsds/1nvh6Dd5HTWQ3RwaC6SBAQiWHj 0SQA==
X-Gm-Message-State: AFeK/H0Twhy6pn9GVP6lbejLQKWuuQgNWoSXZz7uUqnzS+Z7bxfDHdwBGwBc7/OW4dEjvn93SFUnx0Q4XhWy/Q==
X-Received: by 10.28.102.86 with SMTP id a83mr16004520wmc.76.1490728898128; Tue, 28 Mar 2017 12:21:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.40.69 with HTTP; Tue, 28 Mar 2017 12:21:37 -0700 (PDT)
From: Richard Barnes <rlb@ipv.sx>
Date: Tue, 28 Mar 2017 15:21:37 -0400
Message-ID: <CAL02cgQ5MR6o2wWu=NUpneJ8UPmqxkFmBY4Y-+vCUtxvVCBu5g@mail.gmail.com>
To: Trans <trans@ietf.org>
Content-Type: multipart/alternative; boundary="001a114b2ec46df348054bcf5e3e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/u2E6TLeaCFsCVsj79YeP629cW6U>
Subject: [Trans] Mozilla's basic take on Binary Transparency
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Mar 2017 19:21:41 -0000

As I said at the mic, there's some work going on at Mozilla to implement a
form of Binary Transparency, leveraged on top of CT.  Here's the outline:

https://wiki.mozilla.org/Security/Binary_Transparency