CT for Binary Codes
draft-zhang-trans-ct-binary-codes-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Liang Xia , Dacheng Zhang , Daniel Kahn Gillmor , Behcet Sarikaya | ||
| Last updated | 2017-09-07 (Latest revision 2017-03-06) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Dacheng Zhang
Daniel Kahn Gillmor
Behcet Sarikaya
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)