[git] gnupg-doc - branch, master, updated. bf4a2f6e4c1f7378105b79354e48ed8e91ecd14d
by Werner Koch
cvs at cvs.gnupg.org
Wed May 4 17:40:56 CEST 2016
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The GnuPG website and other docs".
The branch, master has been updated
via bf4a2f6e4c1f7378105b79354e48ed8e91ecd14d (commit)
from 70ce98d57b8cc02f1bec2c9169dd3c57a292a1e5 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit bf4a2f6e4c1f7378105b79354e48ed8e91ecd14d
Author: Werner Koch <wk at gnupg.org>
Date: Wed May 4 17:40:09 2016 +0200
drafts: Commit collected changes.
diff --git a/misc/id/common/reference.I-D.irtf-cfrg-eddsa.xml b/misc/id/common/reference.I-D.irtf-cfrg-eddsa.xml
new file mode 100644
index 0000000..7f9f6b6
--- /dev/null
+++ b/misc/id/common/reference.I-D.irtf-cfrg-eddsa.xml
@@ -0,0 +1,24 @@
+<?xml version='1.0' encoding='UTF-8'?>
+
+<reference anchor='I-D.irtf-cfrg-eddsa'>
+<front>
+<title>Edwards-curve Digital Signature Algorithm (EdDSA)</title>
+
+<author initials='S' surname='Josefsson' fullname='Simon Josefsson'>
+ <organization />
+</author>
+
+<author initials='I' surname='Liusvaara' fullname='Ilari Liusvaara'>
+ <organization />
+</author>
+
+<date month='January' day='19' year='2016' />
+
+<abstract><t>The elliptic curve signature scheme Edwards-curve Digital Signature Algorithm (EdDSA) is described. The algorithm is instantiated with recommended parameters for the Curve25519 and Curve448 curves. An example implementation and test vectors are provided.</t></abstract>
+
+</front>
+
+<seriesInfo name='Internet-Draft' value='draft-irtf-cfrg-eddsa-02' />
+<format type='TXT'
+ target='http://www.ietf.org/internet-drafts/draft-irtf-cfrg-eddsa-02.txt' />
+</reference>
diff --git a/misc/id/common/reference.RFC.0822.xml b/misc/id/common/reference.RFC.0822.xml
new file mode 100644
index 0000000..e88b0e3
--- /dev/null
+++ b/misc/id/common/reference.RFC.0822.xml
@@ -0,0 +1,13 @@
+<?xml version='1.0' encoding='UTF-8'?>
+
+<reference anchor='RFC0822' target='http://www.rfc-editor.org/info/rfc822'>
+<front>
+<title>STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES</title>
+<author initials='D.' surname='Crocker' fullname='D. Crocker'><organization /></author>
+<date year='1982' month='August' />
+<abstract><t>This document revises the specifications in RFC 733, in order to serve the needs of the larger and more complex ARPA Internet. Some of RFC 733's features failed to gain adequate acceptance. In order to simplify the standard and the software that follows it, these features have been removed. A different addressing scheme is used, to handle the case of internetwork mail; and the concept of re-transmission has been introduced. Obsoletes RFC 733, NIC 41952.</t></abstract>
+</front>
+<seriesInfo name='STD' value='11'/>
+<seriesInfo name='RFC' value='822'/>
+<seriesInfo name='DOI' value='10.17487/RFC0822'/>
+</reference>
diff --git a/misc/id/common/reference.RFC.5785.xml b/misc/id/common/reference.RFC.5785.xml
new file mode 100644
index 0000000..4cf6c83
--- /dev/null
+++ b/misc/id/common/reference.RFC.5785.xml
@@ -0,0 +1,13 @@
+<?xml version='1.0' encoding='UTF-8'?>
+
+<reference anchor='RFC5785' target='http://www.rfc-editor.org/info/rfc5785'>
+<front>
+<title>Defining Well-Known Uniform Resource Identifiers (URIs)</title>
+<author initials='M.' surname='Nottingham' fullname='M. Nottingham'><organization /></author>
+<author initials='E.' surname='Hammer-Lahav' fullname='E. Hammer-Lahav'><organization /></author>
+<date year='2010' month='April' />
+<abstract><t>This memo defines a path prefix for "well-known locations", "/.well-known/", in selected Uniform Resource Identifier (URI) schemes. [STANDARDS-TRACK]</t></abstract>
+</front>
+<seriesInfo name='RFC' value='5785'/>
+<seriesInfo name='DOI' value='10.17487/RFC5785'/>
+</reference>
diff --git a/misc/id/common/reference.RFC.6189.xml b/misc/id/common/reference.RFC.6189.xml
new file mode 100644
index 0000000..6268e1a
--- /dev/null
+++ b/misc/id/common/reference.RFC.6189.xml
@@ -0,0 +1,14 @@
+<?xml version='1.0' encoding='UTF-8'?>
+
+<reference anchor='RFC6189' target='http://www.rfc-editor.org/info/rfc6189'>
+<front>
+<title>ZRTP: Media Path Key Agreement for Unicast Secure RTP</title>
+<author initials='P.' surname='Zimmermann' fullname='P. Zimmermann'><organization /></author>
+<author initials='A.' surname='Johnston' fullname='A. Johnston' role='editor'><organization /></author>
+<author initials='J.' surname='Callas' fullname='J. Callas'><organization /></author>
+<date year='2011' month='April' />
+<abstract><t>This document defines ZRTP, a protocol for media path Diffie-Hellman exchange to agree on a session key and parameters for establishing unicast Secure Real-time Transport Protocol (SRTP) sessions for Voice over IP (VoIP) applications. The ZRTP protocol is media path keying because it is multiplexed on the same port as RTP and does not require support in the signaling protocol. ZRTP does not assume a Public Key Infrastructure (PKI) or require the complexity of certificates in end devices. For the media session, ZRTP provides confidentiality, protection against man-in-the-middle (MiTM) attacks, and, in cases where the signaling protocol provides end-to-end integrity protection, authentication. ZRTP can utilize a Session Description Protocol (SDP) attribute to provide discovery and authentication through the signaling channel. To provide best effort SRTP, ZRTP utilizes normal RTP/AVP (Audio-Visual Profile) profiles. ZRTP secures media sessions that include a voice media stream and can also secure media sessions that do not include voice by using an optional digital signature. This document is not an Internet Standards Track specification; it is published for informational purposes.</t></abstract>
+</front>
+<seriesInfo name='RFC' value='6189'/>
+<seriesInfo name='DOI' value='10.17487/RFC6189'/>
+</reference>
diff --git a/misc/id/common/reference.RFC.7748.xml b/misc/id/common/reference.RFC.7748.xml
new file mode 100644
index 0000000..d82a086
--- /dev/null
+++ b/misc/id/common/reference.RFC.7748.xml
@@ -0,0 +1,14 @@
+<?xml version='1.0' encoding='UTF-8'?>
+
+<reference anchor='RFC7748' target='http://www.rfc-editor.org/info/rfc7748'>
+<front>
+<title>Elliptic Curves for Security</title>
+<author initials='A.' surname='Langley' fullname='A. Langley'><organization /></author>
+<author initials='M.' surname='Hamburg' fullname='M. Hamburg'><organization /></author>
+<author initials='S.' surname='Turner' fullname='S. Turner'><organization /></author>
+<date year='2016' month='January' />
+<abstract><t>This memo specifies two elliptic curves over prime fields that offer a high level of practical security in cryptographic applications, including Transport Layer Security (TLS). These curves are intended to operate at the ~128-bit and ~224-bit security level, respectively, and are generated deterministically based on a list of required properties.</t></abstract>
+</front>
+<seriesInfo name='RFC' value='7748'/>
+<seriesInfo name='DOI' value='10.17487/RFC7748'/>
+</reference>
diff --git a/misc/id/eddsa-for-openpgp/back.mkd b/misc/id/eddsa-for-openpgp/back.mkd
index 77a16ca..e00e12f 100644
--- a/misc/id/eddsa-for-openpgp/back.mkd
+++ b/misc/id/eddsa-for-openpgp/back.mkd
@@ -74,4 +74,4 @@ other values might also be interesting for other ECC specifications:
# Changes since -03
- - xxxx
+ - Changed reference for EdDSA to CFRG draft.
diff --git a/misc/id/eddsa-for-openpgp/draft-koch-eddsa-for-openpgp-04.txt b/misc/id/eddsa-for-openpgp/draft-koch-eddsa-for-openpgp-04.txt
new file mode 100644
index 0000000..e26533d
--- /dev/null
+++ b/misc/id/eddsa-for-openpgp/draft-koch-eddsa-for-openpgp-04.txt
@@ -0,0 +1,448 @@
+
+
+
+
+Network Working Group W. Koch
+Internet-Draft g10 Code
+Updates: 4880 (if approved) February 28, 2016
+Intended status: Informational
+Expires: August 31, 2016
+
+
+ EdDSA for OpenPGP
+ draft-koch-eddsa-for-openpgp-04
+
+Abstract
+
+ This specification extends OpenPGP with the EdDSA public key
+ algorithm and describes the use of curve Ed25519.
+
+Status of This Memo
+
+ This Internet-Draft is submitted in full conformance with the
+ provisions of BCP 78 and BCP 79.
+
+ Internet-Drafts are working documents of the Internet Engineering
+ Task Force (IETF). Note that other groups may also distribute
+ working documents as Internet-Drafts. The list of current Internet-
+ Drafts is at http://datatracker.ietf.org/drafts/current/.
+
+ Internet-Drafts are draft documents valid for a maximum of six months
+ and may be updated, replaced, or obsoleted by other documents at any
+ time. It is inappropriate to use Internet-Drafts as reference
+ material or to cite them other than as "work in progress."
+
+ This Internet-Draft will expire on August 31, 2016.
+
+Copyright Notice
+
+ Copyright (c) 2016 IETF Trust and the persons identified as the
+ document authors. All rights reserved.
+
+ This document is subject to BCP 78 and the IETF Trust's Legal
+ Provisions Relating to IETF Documents
+ (http://trustee.ietf.org/license-info) in effect on the date of
+ publication of this document. Please review these documents
+ carefully, as they describe your rights and restrictions with respect
+ to this document. Code Components extracted from this document must
+ include Simplified BSD License text as described in Section 4.e of
+ the Trust Legal Provisions and are provided without warranty as
+ described in the Simplified BSD License.
+
+
+
+
+
+Koch Expires August 31, 2016 [Page 1]
+
+Internet-Draft EdDSA for OpenPGP February 2016
+
+
+Table of Contents
+
+ 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
+ 2. Supported Curves . . . . . . . . . . . . . . . . . . . . . . 2
+ 3. Point Format . . . . . . . . . . . . . . . . . . . . . . . . 3
+ 4. Encoding of Public and Private Keys . . . . . . . . . . . . . 3
+ 5. Message Encoding . . . . . . . . . . . . . . . . . . . . . . 4
+ 6. Curve OID . . . . . . . . . . . . . . . . . . . . . . . . . . 4
+ 7. Security Considerations . . . . . . . . . . . . . . . . . . . 5
+ 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
+ 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
+ 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
+ 10.1. Normative References . . . . . . . . . . . . . . . . . . 5
+ 10.2. Informative References . . . . . . . . . . . . . . . . . 6
+ Appendix A. Test vectors . . . . . . . . . . . . . . . . . . . . 6
+ A.1. Sample key . . . . . . . . . . . . . . . . . . . . . . . 6
+ A.2. Sample signature . . . . . . . . . . . . . . . . . . . . 7
+ Appendix B. Point compression flag bytes . . . . . . . . . . . . 7
+ Appendix C. Changes since -03 . . . . . . . . . . . . . . . . . 8
+ Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8
+
+1. Introduction
+
+ The OpenPGP specification in [RFC4880] defines the RSA, Elgamal, and
+ DSA public key algorithms. [RFC6637] adds support for Elliptic Curve
+ Cryptography and specifies the ECDSA and ECDH algorithms. Due to
+ patent reasons no point compression was defined.
+
+ This document specifies how to use the EdDSA public key signature
+ algorithm [I-D.irtf-cfrg-eddsa] with the OpenPGP standard. It
+ defines a new signature algorithm named EdDSA and specifies how to
+ use the Ed25519 curve with EdDSA. This algorithm uses a custom point
+ compression method. There are three main advantages of the EdDSA
+ algorithm: It does not require the use of a unique random number for
+ each signature, there are no padding or truncation issues as with
+ ECDSA, and it is more resilient to side-channel attacks.
+
+ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
+ "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
+ document are to be interpreted as described in [RFC2119].
+
+2. Supported Curves
+
+ This document references the Curve "Ed25519" which is the Edwards
+ form of "Curve25519" ([RFC7748]) and originally specified in the same
+ paper as the "EdDSA" algorithm ([ED25519]). For the full
+ specification see [I-D.irtf-cfrg-eddsa].
+
+
+
+
+Koch Expires August 31, 2016 [Page 2]
+
+Internet-Draft EdDSA for OpenPGP February 2016
+
+
+ Other curves may be used by using a specific OID for the curve and
+ its EdDSA parameters.
+
+ The following public key algorithm IDs are added to expand section
+ 9.1 of [RFC4880], "Public-Key Algorithms":
+
+ +-------+-----------------------------+
+ | ID | Description of Algorithm |
+ +-------+-----------------------------+
+ | TBD1 | EdDSA public key algorithm |
+ +-------+-----------------------------+
+
+ Compliant applications MUST support EdDSA with the curve Ed25519.
+ Applications MAY support other curves as long as a dedicated OID for
+ using that curve with EdDSA is used.
+
+3. Point Format
+
+ The EdDSA algorithm defines a specific point compression format. To
+ indicate the use of this compression format and to make sure that the
+ key can be represented in the Multiprecision Integer (MPI) format of
+ [RFC4880] the octet string specifying the point is prefixed with the
+ octet 0x40. This encoding is an extension of the encoding given in
+ [RFC6637] which uses 0x04 to indicate an uncompressed point.
+
+ For example, the length of a public key for the curve Ed25519 is 263
+ bit: 7 bit to represent the 0x40 prefix octet and 32 octets for the
+ native value of the public key.
+
+4. Encoding of Public and Private Keys
+
+ The following algorithm specific packets are added to Section 5.5.2
+ of [RFC4880], "Public-Key Packet Formats", to support EdDSA.
+
+ Algorithm-Specific Fields for EdDSA keys:
+
+ o a variable length field containing a curve OID, formatted as
+ follows:
+
+ * a one-octet size of the following field; values 0 and 0xFF are
+ reserved for future extensions,
+
+ * octets representing a curve OID, defined in Section 6.
+
+ o MPI of an EC point representing a public key Q as described under
+ Point Format above.
+
+
+
+
+
+Koch Expires August 31, 2016 [Page 3]
+
+Internet-Draft EdDSA for OpenPGP February 2016
+
+
+ The following algorithm specific packets are added to Section 5.5.3
+ of [RFC4880], "Secret-Key Packet Formats", to support EdDSA.
+
+ Algorithm-Specific Fields for EdDSA keys:
+
+ o an MPI of an integer representing the secret key, which is a
+ scalar of the public EC point.
+
+ The version 4 packet format MUST be used.
+
+5. Message Encoding
+
+ Section 5.2.3 of [RFC4880], "Version 4 Signature Packet Format"
+ specifies formats. To support EdDSA no change is required, the MPIs
+ representing the R and S value are encoded as MPIs in the same way as
+ done for the DSA and ECDSA algorithms; in particular the Algorithm-
+ Specific Fields for an EdDSA signature are:
+
+ - MPI of EdDSA value r.
+
+ - MPI of EdDSA value s.
+
+ Note that the compressed version of R and S as specified for EdDSA
+ ([I-D.irtf-cfrg-eddsa]) is used.
+
+ The version 3 signature format MUST NOT be used with EdDSA.
+
+ Although that algorithm allows arbitrary data as input, its use with
+ OpenPGP requires that a digest of the message is used as input. See
+ section 5.2.4 of [RFC4880], "Computing Signatures" for details.
+ Truncation of the resulting digest is never applied; the resulting
+ digest value is used verbatim as input to the EdDSA algorithm.
+
+6. Curve OID
+
+ The EdDSA key parameter curve OID is an array of octets that defines
+ a named curve. The table below specifies the exact sequence of bytes
+ for each named curve referenced in this document:
+
+ +------------------------+------+------------------------+----------+
+ | OID | Len | Encoding in hex format | Name |
+ +------------------------+------+------------------------+----------+
+ | 1.3.6.1.4.1.11591.15.1 | 9 | 2B 06 01 04 01 DA 47 | Ed25519 |
+ | | | 0F 01 | |
+ +------------------------+------+------------------------+----------+
+
+ See [RFC6637] for a description of the OID encoding given in the
+ second and third columns.
+
+
+
+Koch Expires August 31, 2016 [Page 4]
+
+Internet-Draft EdDSA for OpenPGP February 2016
+
+
+7. Security Considerations
+
+ The security considerations of [RFC4880] apply accordingly.
+
+ Although technically possible the use of EdDSA with digest algorithms
+ weaker than SHA-256 (e.g. SHA-1) is not suggested.
+
+8. IANA Considerations
+
+ IANA is requested to assign an algorithm number from the OpenPGP
+ Public-Key Algorithms range, or the "namespace" in the terminology of
+ [RFC5226], that was created by [RFC4880]. See section 2.
+
+ +-------+-----------------------------+------------+
+ | ID | Algorithm | Reference |
+ +-------+-----------------------------+------------+
+ | TBD1 | EdDSA public key algorithm | This doc |
+ +-------+-----------------------------+------------+
+
+ [Notes to RFC-Editor: Please remove the table above on publication.
+ It is desirable not to reuse old or reserved algorithms because some
+ existing tools might print a wrong description. A higher number is
+ also an indication for a newer algorithm. As of now 22 is the next
+ free number.]
+
+9. Acknowledgments
+
+ The author would like to acknowledge the help of the individuals who
+ kindly voiced their opinions on the IETF OpenPGP and GnuPG mailing
+ lists, in particular, the help of Andrey Jivsov, Jon Callas, and
+ NIIBE Yutaka.
+
+10. References
+
+10.1. Normative References
+
+ [I-D.irtf-cfrg-eddsa]
+ Josefsson, S. and I. Liusvaara, "Edwards-curve Digital
+ Signature Algorithm (EdDSA)", draft-irtf-cfrg-eddsa-02
+ (work in progress), January 2016.
+
+ [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
+ Requirement Levels", BCP 14, RFC 2119, March 1997.
+
+ [RFC4880] Callas, J., Donnerhacke, L., Finney, H., Shaw, D., and R.
+ Thayer, "OpenPGP Message Format", RFC 4880, November 2007.
+
+
+
+
+
+Koch Expires August 31, 2016 [Page 5]
+
+Internet-Draft EdDSA for OpenPGP February 2016
+
+
+ [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
+ IANA Considerations Section in RFCs", BCP 26, RFC 5226,
+ May 2008.
+
+ [RFC6637] Jivsov, A., "Elliptic Curve Cryptography (ECC) in
+ OpenPGP", RFC 6637, June 2012.
+
+10.2. Informative References
+
+ [ED25519] Bernstein, D., Duif, N., Lange, T., Schwabe, P., and B.
+ Yang, "High-speed high-security signatures", Journal of
+ Cryptographic Engineering Volume 2, Issue 2, pp. 77-89,
+ September 2011,
+ <http://dx.doi.org/10.1007/s13389-012-0027-1>.
+
+ [RFC7748] Langley, A., Hamburg, M., and S. Turner, "Elliptic Curves
+ for Security", RFC 7748, DOI 10.17487/RFC7748, January
+ 2016, <http://www.rfc-editor.org/info/rfc7748>.
+
+Appendix A. Test vectors
+
+ For help implementing this specification a non-normative example is
+ given. This example assumes that the algorithm id for EdDSA (TBD1)
+ will be 22.
+
+A.1. Sample key
+
+ The secret key used for this example is:
+
+ D: 1a8b1ff05ded48e18bf50166c664ab023ea70003d78d9e41f5758a91d850f8d2
+
+ Note that this is the raw secret key used as input to the EdDSA
+ signing operation. The key was created on 2014-08-19 14:28:27 and
+ thus the fingerprint of the OpenPGP key is:
+
+ C959 BDBA FA32 A2F8 9A15 3B67 8CFD E121 9796 5A9A
+
+ The algorithm specific input parameters without the MPI length
+ headers are:
+
+ oid: 2b06010401da470f01
+
+ q: 403f098994bdd916ed4053197934e4a87c80733a1280d62f8010992e43ee3b2406
+
+ The entire public key packet is thus:
+
+
+
+
+
+
+Koch Expires August 31, 2016 [Page 6]
+
+Internet-Draft EdDSA for OpenPGP February 2016
+
+
+ 98 33 04 53 f3 5f 0b 16 09 2b 06 01 04 01 da 47
+ 0f 01 01 07 40 3f 09 89 94 bd d9 16 ed 40 53 19
+ 79 34 e4 a8 7c 80 73 3a 12 80 d6 2f 80 10 99 2e
+ 43 ee 3b 24 06
+
+A.2. Sample signature
+
+ The signature is created using the sample key over the input data
+ "OpenPGP" on 2015-09-16 12:24:53 and thus the input to the hash
+ function is:
+
+ m: 4f70656e504750040016080006050255f95f9504ff0000000c
+
+ Using the SHA-256 hash algorithm yields the digest:
+
+ d: f6220a3f757814f4c2176ffbb68b00249cd4ccdc059c4b34ad871f30b1740280
+
+ Which is fed into the EdDSA signature function and yields this
+ signature:
+
+ r: 56f90cca98e2102637bd983fdb16c131dfd27ed82bf4dde5606e0d756aed3366
+
+ s: d09c4fa11527f038e0f57f2201d82f2ea2c9033265fa6ceb489e854bae61b404
+
+ The entire signature packet is thus:
+
+ 88 5e 04 00 16 08 00 06 05 02 55 f9 5f 95 00 0a
+ 09 10 8c fd e1 21 97 96 5a 9a f6 22 01 00 56 f9
+ 0c ca 98 e2 10 26 37 bd 98 3f db 16 c1 31 df d2
+ 7e d8 2b f4 dd e5 60 6e 0d 75 6a ed 33 66 01 00
+ d0 9c 4f a1 15 27 f0 38 e0 f5 7f 22 01 d8 2f 2e
+ a2 c9 03 32 65 fa 6c eb 48 9e 85 4b ae 61 b4 04
+
+Appendix B. Point compression flag bytes
+
+ This specification introduces the new flag byte 0x40 to indicate the
+ point compression format. The value has been chosen so that the high
+ bit is not cleared and thus to avoid accidental sign extension. Two
+ other values might also be interesting for other ECC specifications:
+
+ Flag Description
+ ---- -----------
+ 0x04 Standard flag for uncompressed format
+ 0x40 Native point format of the curve follows
+ 0x41 Only X coordinate follows.
+ 0x42 Only Y coordinate follows.
+
+
+
+
+
+Koch Expires August 31, 2016 [Page 7]
+
+Internet-Draft EdDSA for OpenPGP February 2016
+
+
+Appendix C. Changes since -03
+
+ o Changed reference for EdDSA to CFRG draft.
+
+Author's Address
+
+ Werner Koch
+ g10 Code
+
+ Email: wk at gnupg.org
+ URI: https://g10code.com
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Koch Expires August 31, 2016 [Page 8]
diff --git a/misc/id/eddsa-for-openpgp/middle.mkd b/misc/id/eddsa-for-openpgp/middle.mkd
index 2dfeb92..0d9a002 100644
--- a/misc/id/eddsa-for-openpgp/middle.mkd
+++ b/misc/id/eddsa-for-openpgp/middle.mkd
@@ -6,7 +6,7 @@ Elliptic Curve Cryptography and specifies the ECDSA and ECDH
algorithms. Due to patent reasons no point compression was defined.
This document specifies how to use the EdDSA public key signature
-algorithm [](#I-D.josefsson-eddsa-ed25519) with the OpenPGP standard.
+algorithm [](#I-D.irtf-cfrg-eddsa) with the OpenPGP standard.
It defines a new signature algorithm named EdDSA and specifies how to
use the Ed25519 curve with EdDSA. This algorithm uses a custom point
compression method. There are three main advantages of the EdDSA
@@ -22,9 +22,9 @@ document are to be interpreted as described in [](#RFC2119).
# Supported Curves
This document references the Curve "Ed25519" which is the Edwards form
-of "Curve25519" and specified in the same paper as the "EdDSA"
-algorithm ([](#ED25519)). For the full specification see
-[](#I-D.josefsson-eddsa-ed25519).
+of "Curve25519" ([](#RFC7748)) and originally specified in the same
+paper as the "EdDSA" algorithm ([](#ED25519)). For the full
+specification see [](#I-D.irtf-cfrg-eddsa).
Other curves may be used by using a specific OID for the curve and its
EdDSA parameters.
@@ -95,7 +95,7 @@ Algorithm-Specific Fields for an EdDSA signature are:
- MPI of EdDSA value s.
Note that the compressed version of R and S as specified for EdDSA
-([](#I-D.josefsson-eddsa-ed25519)) is used.
+([](#I-D.irtf-cfrg-eddsa)) is used.
The version 3 signature format MUST NOT be used with EdDSA.
diff --git a/misc/id/eddsa-for-openpgp/template.xml b/misc/id/eddsa-for-openpgp/template.xml
index d27accc..484e6cb 100644
--- a/misc/id/eddsa-for-openpgp/template.xml
+++ b/misc/id/eddsa-for-openpgp/template.xml
@@ -8,9 +8,10 @@
<!ENTITY rfc.4880 PUBLIC '' '../common/reference.RFC.4880.xml'>
<!ENTITY rfc.5226 PUBLIC '' '../common/reference.RFC.5226.xml'>
<!ENTITY rfc.6637 PUBLIC '' '../common/reference.RFC.6637.xml'>
+ <!ENTITY rfc.7748 PUBLIC '' '../common/reference.RFC.7748.xml'>
<!ENTITY ed25519 PUBLIC '' '../common/reference.ED25519.xml'>
- <!ENTITY eddsaed25519
- PUBLIC '' '../common/reference.I-D.josefsson-eddsa-ed25519.xml'>
+ <!ENTITY eddsa
+ PUBLIC '' '../common/reference.I-D.irtf-cfrg-eddsa.xml'>
]>
@@ -36,7 +37,7 @@
</address>
</author>
- <date month="Foo" year="2015" />
+ <date month="February" year="2016" />
<area>Security</area>
<abstract>
@@ -50,7 +51,7 @@
<back>
<references title="Normative References">
- &eddsaed25519;
+ &eddsa;
&rfc.4880;
&rfc.6637;
&rfc.5226;
@@ -58,6 +59,7 @@
</references>
<references title="Informative References">
&ed25519;
+ &rfc.7748;
</references>
&pandocBack;
</back>
-----------------------------------------------------------------------
Summary of changes:
misc/id/common/reference.I-D.irtf-cfrg-eddsa.xml | 24 ++++++
misc/id/common/reference.RFC.0822.xml | 13 ++++
misc/id/common/reference.RFC.5785.xml | 13 ++++
misc/id/common/reference.RFC.6189.xml | 14 ++++
misc/id/common/reference.RFC.7748.xml | 14 ++++
misc/id/eddsa-for-openpgp/back.mkd | 2 +-
...-03.txt => draft-koch-eddsa-for-openpgp-04.txt} | 88 +++++++++++-----------
misc/id/eddsa-for-openpgp/middle.mkd | 10 +--
misc/id/eddsa-for-openpgp/template.xml | 10 ++-
9 files changed, 134 insertions(+), 54 deletions(-)
create mode 100644 misc/id/common/reference.I-D.irtf-cfrg-eddsa.xml
create mode 100644 misc/id/common/reference.RFC.0822.xml
create mode 100644 misc/id/common/reference.RFC.5785.xml
create mode 100644 misc/id/common/reference.RFC.6189.xml
create mode 100644 misc/id/common/reference.RFC.7748.xml
copy misc/id/eddsa-for-openpgp/{draft-koch-eddsa-for-openpgp-03.txt => draft-koch-eddsa-for-openpgp-04.txt} (84%)
hooks/post-receive
--
The GnuPG website and other docs
http://git.gnupg.org
More information about the Gnupg-commits
mailing list