CT for Binary Codes
draft-zhang-trans-ct-binary-codes-04

Document Type Expired Internet-Draft (individual)
Last updated 2017-09-07 (latest revision 2017-03-06)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-zhang-trans-ct-binary-codes-04.txt

Abstract

This document proposes a solution extending the Certificate Transparency protocol [I-D.ietf-trans-rfc6962-bis] for transparently logging the software binary codes (BC)or its digest with their signature, to enable anyone to monitor and audit the software provider activity and notice the distribution of suspect software as well as to audit the BC logs themselves. The solution is called "Binary Transparency" in this document.

Authors

Liang Xia (frank.xialiang@huawei.com)
Dacheng Zhang (dacheng.zhang@huawei.com)
Daniel Gillmor (dkg@fifthhorseman.net)
Behcet Sarikaya (sarikaya@ieee.org)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)