| < draft-zhang-trans-ct-binary-codes-00.txt | draft-zhang-trans-ct-binary-codes-01.txt > | |||
|---|---|---|---|---|
| Network Working Group D. Zhang | Network Working Group D. Zhang | |||
| Internet-Draft Huawei | Internet-Draft Huawei | |||
| Intended status: Experimental October 27, 2014 | Intended status: Experimental D. Gillmor | |||
| Expires: April 30, 2015 | Expires: June 26, 2015 CMRG | |||
| D. He | ||||
| Huawei | ||||
| December 23, 2014 | ||||
| CT for Binary Codes | CT for Binary Codes | |||
| draft-zhang-trans-ct-binary-codes-00 | draft-zhang-trans-ct-binary-codes-01 | |||
| Abstract | Abstract | |||
| This document proposes a solution to use CT for publishing softwares/ | This document proposes a solution to use CT for publishing softwares/ | |||
| binary codes and their signatuers. | binary codes and their signatuers. | |||
| Requirements Language | Requirements Language | |||
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
| "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | |||
| skipping to change at page 1, line 37 ¶ | skipping to change at page 1, line 40 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on April 30, 2015. | This Internet-Draft will expire on June 26, 2015. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2014 IETF Trust and the persons identified as the | Copyright (c) 2014 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 2, line 24 ¶ | skipping to change at page 2, line 27 ¶ | |||
| 3.2. Another Scenarios . . . . . . . . . . . . . . . . . . . . 3 | 3.2. Another Scenarios . . . . . . . . . . . . . . . . . . . . 3 | |||
| 4. Log Format and Operation . . . . . . . . . . . . . . . . . . 3 | 4. Log Format and Operation . . . . . . . . . . . . . . . . . . 3 | |||
| 4.1. Log Entries . . . . . . . . . . . . . . . . . . . . . . . 3 | 4.1. Log Entries . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 4.2. Structure of the Signed Certificate Timestamp . . . . . . 5 | 4.2. Structure of the Signed Certificate Timestamp . . . . . . 5 | |||
| 5. Log Client Messages . . . . . . . . . . . . . . . . . . . . . 6 | 5. Log Client Messages . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 5.1. Add Binary and Certificate Chain to Log . . . . . . . . . 6 | 5.1. Add Binary and Certificate Chain to Log . . . . . . . . . 6 | |||
| 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 | 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 | |||
| 7. Security Considerations . . . . . . . . . . . . . . . . . . . 7 | 7. Security Considerations . . . . . . . . . . . . . . . . . . . 7 | |||
| 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 | 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 | |||
| 9. Normative References . . . . . . . . . . . . . . . . . . . . 7 | 9. Normative References . . . . . . . . . . . . . . . . . . . . 7 | |||
| Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 | |||
| 1. Introduction | 1. Introduction | |||
| Digital signatures have been widely used in software distributions to | Digital signatures have been widely used in software distributions to | |||
| demonstrate the authenticity of softwares. Through verifying | demonstrate the authenticity of softwares. Through verifying | |||
| signatures, end users can could ensure that the softwares they got | signatures, end users can could ensure that the softwares they got | |||
| are provided by legal organizations and never modified during the | are provided by legal organizations and never modified during the | |||
| delivery. If an end user does not have a direct trust relationship | delivery. If an end user does not have a direct trust relationship | |||
| with the software provider, an authentication chain need to be | with the software provider, an authentication chain need to be | |||
| generated from the key used for generating the signature to a trust | generated from the key used for generating the signature to a trust | |||
| skipping to change at page 8, line 5 ¶ | skipping to change at page 8, line 5 ¶ | |||
| Laurie, B., Langley, A., Kasper, E., and R. Stradling, | Laurie, B., Langley, A., Kasper, E., and R. Stradling, | |||
| "Certificate Transparency", draft-ietf-trans- | "Certificate Transparency", draft-ietf-trans- | |||
| rfc6962-bis-04 (work in progress), July 2014. | rfc6962-bis-04 (work in progress), July 2014. | |||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", BCP 14, RFC 2119, March 1997. | Requirement Levels", BCP 14, RFC 2119, March 1997. | |||
| [RFC5652] Housley, R., "Cryptographic Message Syntax (CMS)", STD 70, | [RFC5652] Housley, R., "Cryptographic Message Syntax (CMS)", STD 70, | |||
| RFC 5652, September 2009. | RFC 5652, September 2009. | |||
| Author's Address | Authors' Addresses | |||
| Dacheng Zhang | Dacheng Zhang | |||
| Huawei | Huawei | |||
| Email: zhangdacheng@huawei.com | Email: zhangdacheng@huawei.com | |||
| Daniel Kahn Gillmor | ||||
| CMRG | ||||
| Email: dkg@fifthhorseman.net | ||||
| Danping He | ||||
| Huawei | ||||
| Email: ana.hedanping@huawei.com | ||||
| End of changes. 6 change blocks. | ||||
| 6 lines changed or deleted | 9 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||