Microsoft

mbj@microsoft.com https://self-issued.info/

Security COSE Working Group Cryptography Digital Signature Encryption W3C World Wide Web Consortium WebAuthn Web Authentication FIDO Alliance FIDO FIDO2 CTAP CTAP2 The W3C Web Authentication (WebAuthn) specification and the FIDO Alliance FIDO2 Client to Authenticator Protocol (CTAP) specification use CBOR Object Signing and Encryption (COSE) algorithm identifiers. This specification registers the following algorithms (which are used by WebAuthn and CTAP implementations) in the IANA "COSE Algorithms" registry: RSASSA-PKCS1-v1_5 using SHA-256, SHA-384, SHA-512, and SHA-1; and Elliptic Curve Digital Signature Algorithm (ECDSA) using the secp256k1 curve and SHA-256. It registers the secp256k1 elliptic curve in the IANA "COSE Elliptic Curves" registry. Also, for use with JSON Object Signing and Encryption (JOSE), it registers the algorithm ECDSA using the secp256k1 curve and SHA-256 in the IANA "JSON Web Signature and Encryption Algorithms" registry and the secp256k1 elliptic curve in the IANA "JSON Web Key Elliptic Curve" registry.

Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at .

Copyright Notice Copyright (c) 2020 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 () 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.

Table of Contents

• .  Introduction
  • .  Requirements Notation and Conventions
• .  RSASSA-PKCS1-v1_5 Signature Algorithm
• .  Using secp256k1 with JOSE and COSE
  • .  JOSE and COSE secp256k1 Curve Key Representations
  • .  ECDSA Signature with secp256k1 Curve
  • .  Other Uses of the secp256k1 Elliptic Curve
• .  IANA Considerations
  • .  COSE Algorithms Registrations
  • .  COSE Elliptic Curves Registrations
  • .  JOSE Algorithms Registrations
  • .  JSON Web Key Elliptic Curves Registrations
• .  Security Considerations
  • .  RSA Key Size Security Considerations
  • .  RSASSA-PKCS1-v1_5 with SHA-2 Security Considerations
  • .  RSASSA-PKCS1-v1_5 with SHA-1 Security Considerations
  • .  secp256k1 Security Considerations
• .  References
  • .  Normative References
  • .  Informative References
• Acknowledgements
• Author's Address

Introduction This specification defines how to use several algorithms with CBOR Object Signing and Encryption (COSE) that are used by implementations of the W3C Web Authentication (WebAuthn) and FIDO Alliance FIDO2 Client to Authenticator Protocol (CTAP) specifications. This specification registers these algorithms in the IANA "COSE Algorithms" registry and registers an elliptic curve in the IANA "COSE Elliptic Curves" registry . This specification also registers a corresponding algorithm for use with JSON Object Signing and Encryption (JOSE) in the IANA "JSON Web Signature and Encryption Algorithms" registry and registers an elliptic curve in the IANA "JSON Web Key Elliptic Curve" registry .

Requirements Notation and Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

RSASSA-PKCS1-v1_5 Signature Algorithm The RSASSA-PKCS1-v1_5 signature algorithm is defined in . The RSASSA-PKCS1-v1_5 signature algorithm is parameterized with a hash function (h). A key of size 2048 bits or larger MUST be used with these algorithms. Implementations need to check that the key type is 'RSA' when creating or verifying a signature. The RSASSA-PKCS1-v1_5 algorithms specified in this document are in the following table. RSASSA-PKCS1-v1_5 Algorithm Values

Name	Value	Hash	Description	Recommended
RS256	-257	SHA-256	RSASSA-PKCS1-v1_5 using SHA-256	No
RS384	-258	SHA-384	RSASSA-PKCS1-v1_5 using SHA-384	No
RS512	-259	SHA-512	RSASSA-PKCS1-v1_5 using SHA-512	No
RS1	-65535	SHA-1	RSASSA-PKCS1-v1_5 using SHA-1	Deprecated

Security considerations for use of the first three algorithms are in . Security considerations for use of the last algorithm are in . Note that these algorithms are already present in the IANA "JSON Web Signature and Encryption Algorithms" registry , and so these registrations are only for the IANA "COSE Algorithms" registry .

Using secp256k1 with JOSE and COSE This section defines algorithm encodings and representations enabling the Standards for Efficient Cryptography Group (SECG) elliptic curve secp256k1 to be used for JOSE and COSE messages.

JOSE and COSE secp256k1 Curve Key Representations The SECG elliptic curve secp256k1 is represented in a JSON Web Key (JWK) using these values:

• kty: EC
• crv: secp256k1

plus the values needed to represent the curve point, as defined in . As a compressed point encoding representation is not defined for JWK elliptic curve points, the uncompressed point encoding defined there MUST be used. The x and y values represented MUST both be exactly 256 bits, with any leading zeros preserved. Other optional values such as alg MAY also be present. It is represented in a COSE_Key using these values:

• kty (1): EC2 (2)
• crv (-1): secp256k1 (8)

plus the values needed to represent the curve point, as defined in . Either the uncompressed or compressed point encoding representations defined there can be used. The x value represented MUST be exactly 256 bits, with any leading zeros preserved. If the uncompressed representation is used, the y value represented MUST likewise be exactly 256 bits, with any leading zeros preserved; if the compressed representation is used, the y value is a boolean value, as specified in . Other optional values such as alg (3) MAY also be present.

ECDSA Signature with secp256k1 Curve The ECDSA signature algorithm is defined in . This specification defines the ES256K algorithm identifier, which is used to specify the use of ECDSA with the secp256k1 curve and the SHA-256 cryptographic hash function. Implementations need to check that the key type is EC for JOSE or EC2 (2) for COSE and that the curve of the key is secp256k1 when creating or verifying a signature. The ECDSA secp256k1 SHA-256 digital signature is generated as follows:

1. Generate a digital signature of the JWS Signing Input or the COSE Sig_structure using ECDSA secp256k1 SHA-256 with the desired private key. The output will be the pair (R, S), where R and S are 256-bit unsigned integers.
2. Turn R and S into octet sequences in big-endian order, with each array being 32 octets long. The octet sequence representations MUST NOT be shortened to omit any leading zero octets contained in the values.
3. Concatenate the two octet sequences in the order R and then S. (Note that many ECDSA implementations will directly produce this concatenation as their output.)
4. The resulting 64-octet sequence is the JWS Signature or COSE signature value.

Implementations SHOULD use a deterministic algorithm to generate the ECDSA nonce, k, such as the algorithm defined in . However, in situations where devices are vulnerable to physical attacks, deterministic ECDSA has been shown to be susceptible to fault injection attacks . Where this is a possibility, implementations SHOULD implement appropriate countermeasures. Where there are specific certification requirements (such as FIPS approval), implementors should check whether deterministic ECDSA is an approved nonce generation method. The ECDSA secp256k1 SHA-256 algorithm specified in this document uses these identifiers: ECDSA Algorithm Values

Name	Value	Description	Recommended
ES256K	-47	ECDSA using secp256k1 curve and SHA-256	No

When using a JWK or COSE_Key for this algorithm, the following checks are made:

• The kty field MUST be present, and it MUST be EC for JOSE or EC2 for COSE.
• The crv field MUST be present, and it MUST represent the secp256k1 elliptic curve.
• If the alg field is present, it MUST represent the ES256K algorithm.
• If the key_ops field is present, it MUST include sign when creating an ECDSA signature.
• If the key_ops field is present, it MUST include verify when verifying an ECDSA signature.
• If the JWK use field is present, its value MUST be sig.

Other Uses of the secp256k1 Elliptic Curve This specification defines how to use the secp256k1 curve for ECDSA signatures for both JOSE and COSE implementations. While in theory the curve could also be used for ECDH-ES key agreement, it is beyond the scope of this specification to state whether this is or is not advisable. Thus, whether or not to recommend its use with ECDH-ES is left for experts to decide in future specifications. When used for ECDSA, the secp256k1 curve MUST be used only with the ES256K algorithm identifier and not any others, including not with the COSE ES256 identifier. Note that the ES256K algorithm identifier needed to be introduced for JOSE to sign with the secp256k1 curve because the JOSE ES256 algorithm is defined to be used only with the P-256 curve. The COSE treatment of how to sign with secp256k1 is intentionally parallel to that for JOSE, where the secp256k1 curve MUST be used with the ES256K algorithm identifier.

IANA Considerations

COSE Algorithms Registrations IANA has registered the following values in the "COSE Algorithms" registry .

Name:

RS256

Value:

-257

Description:

RSASSA-PKCS1-v1_5 using SHA-256

Change Controller:

IESG

Reference:

of RFC 8812

Recommended:

No

Name:

RS384

Value:

-258

Description:

RSASSA-PKCS1-v1_5 using SHA-384

Change Controller:

IESG

Reference:

of RFC 8812

Recommended:

No

Name:

RS512

Value:

-259

Description:

RSASSA-PKCS1-v1_5 using SHA-512

Change Controller:

IESG

Reference:

of RFC 8812

Recommended:

No

Name:

RS1

Value:

-65535

Description:

RSASSA-PKCS1-v1_5 using SHA-1

Change Controller:

IESG

Reference:

of RFC 8812

Recommended:

Deprecated

Name:

ES256K

Value:

-47

Description:

ECDSA using secp256k1 curve and SHA-256

Change Controller:

IESG

Reference:

of RFC 8812

Recommended:

No

COSE Elliptic Curves Registrations IANA has registered the following value in the "COSE Elliptic Curves" registry .

Name:

secp256k1

Value:

8

Key Type:

EC2

Description:

SECG secp256k1 curve

Change Controller:

IESG

Reference:

of RFC 8812

Recommended:

No

JOSE Algorithms Registrations IANA has registered the following value in the "JSON Web Signature and Encryption Algorithms" registry .

Algorithm Name:

ES256K

Algorithm Description:

ECDSA using secp256k1 curve and SHA-256

Algorithm Usage Location(s):

alg

JOSE Implementation Requirements:

Optional

Change Controller:

IESG

Reference:

of RFC 8812

Algorithm Analysis Document(s):

JSON Web Key Elliptic Curves Registrations IANA has registered the following value in the "JSON Web Key Elliptic Curve" registry .

Curve Name:

secp256k1

Curve Description:

SECG secp256k1 curve

JOSE Implementation Requirements:

Optional

Change Controller:

IESG

Specification Document(s):

of RFC 8812

Security Considerations

RSA Key Size Security Considerations The security considerations on key sizes for RSA algorithms from also apply to the RSA algorithms in this specification.

RSASSA-PKCS1-v1_5 with SHA-2 Security Considerations The security considerations on the use of RSASSA-PKCS1-v1_5 with SHA-2 hash functions (SHA-256, SHA-384, and SHA-512) from also apply to their use in this specification. For that reason, these algorithms are registered as being "Not Recommended". Likewise, the exponent restrictions described in also apply.

RSASSA-PKCS1-v1_5 with SHA-1 Security Considerations The security considerations on the use of the SHA-1 hash function from apply in this specification. For that reason, the "RS1" algorithm is registered as "Deprecated". Likewise, the exponent restrictions described in also apply. A COSE algorithm identifier for this algorithm is nonetheless being registered because deployed Trusted Platform Modules (TPMs) continue to use it; therefore, WebAuthn implementations need a COSE algorithm identifier for "RS1" when TPM attestations using this algorithm are being represented. New COSE applications and protocols MUST NOT use this algorithm.

secp256k1 Security Considerations Care should be taken that a secp256k1 key is not mistaken for a P-256 key, given that their representations are the same except for the crv value. As described in , we currently do not have any way to deal with this attack except to restrict the set of curves that can be used. The procedures and security considerations described in the , , and specifications apply to implementations of this specification. Timing side-channel attacks are possible if the implementation of scalar multiplication over the curve does not execute in constant time. There are theoretical weaknesses with this curve that could result in future attacks. While these potential weaknesses are not unique to this curve, they are the reason that this curve is registered as "Recommended: No".

References Normative References National Institute of Standards and Technology (NIST) In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. This document includes security considerations for the SHA-0 and SHA-1 message digest algorithm. This document is not an Internet Standards Track specification; it is published for informational purposes. JSON Web Signature (JWS) represents content secured with digital signatures or Message Authentication Codes (MACs) using JSON-based data structures. Cryptographic algorithms and identifiers for use with this specification are described in the separate JSON Web Algorithms (JWA) specification and an IANA registry defined by that specification. Related encryption capabilities are described in the separate JSON Web Encryption (JWE) specification. A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data structure that represents a cryptographic key. This specification also defines a JWK Set JSON data structure that represents a set of JWKs. Cryptographic algorithms and identifiers for use with this specification are described in the separate JSON Web Algorithms (JWA) specification and IANA registries established by that specification. This specification registers cryptographic algorithms and identifiers to be used with the JSON Web Signature (JWS), JSON Web Encryption (JWE), and JSON Web Key (JWK) specifications. It defines several IANA registries for these identifiers. This document provides recommendations for the implementation of public-key cryptography based on the RSA algorithm, covering cryptographic primitives, encryption schemes, signature schemes with appendix, and ASN.1 syntax for representing keys and for identifying the schemes. This document represents a republication of PKCS #1 v2.2 from RSA Laboratories' Public-Key Cryptography Standards (PKCS) series. By publishing this RFC, change control is transferred to the IETF. This document also obsoletes RFC 3447. Concise Binary Object Representation (CBOR) is a data format designed for small code size and small message size. There is a need for the ability to have basic security services defined for this data format. This document defines the CBOR Object Signing and Encryption (COSE) protocol. This specification describes how to create and process signatures, message authentication codes, and encryption using CBOR for serialization. This specification additionally describes how to represent cryptographic keys using CBOR. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. The CBOR Object Signing and Encryption (COSE) specification defines cryptographic message encodings using Concise Binary Object Representation (CBOR). This specification defines algorithm encodings and representations enabling RSA algorithms to be used for COSE messages. Encodings are specified for the use of RSA Probabilistic Signature Scheme (RSASSA-PSS) signatures, RSA Encryption Scheme - Optimal Asymmetric Encryption Padding (RSAES-OAEP) encryption, and RSA keys. Standards for Efficient Cryptography Group Standards for Efficient Cryptography Group Informative References Google

cbrand@google.com

Google

aczeskis@google.com

Yubico

jakob@yubico.com

Microsoft

mbj@microsoft.com http://self-issued.info/

Microsoft

akshayku@microsoft.com

Nok Nok Labs

rolf@noknok.com

FIDO Alliance

adam@fidoalliance.org

OneSpan

johan.verrept@onespan.com

FIDO Alliance Proposed Standard Münster University of Applied Sciences Ruhr University Bochum Münster University of Applied Sciences Federal Office for Information Security Ruhr University Bochum 2018 IEEE European Symposium on Security and Privacy (EuroS&P) IANA IANA IANA IANA Kudelski Security Research This document defines a deterministic digital signature generation procedure. Such signatures are compatible with standard Digital Signature Algorithm (DSA) and Elliptic Curve Digital Signature Algorithm (ECDSA) digital signatures and can be processed with unmodified verifiers, which need not be aware of the procedure described therein. Deterministic signatures retain the cryptographic security features associated with digital signatures but can be more easily implemented in various environments, since they do not need access to a source of high-quality randomness. Google

balfanz@google.com

Google

aczeskis@google.com

Google

Jeff.Hodges@paypal.com

Mozilla

jc@mozilla.com

Microsoft

mbj@microsoft.com http://self-issued.info/

Microsoft

akshayku@microsoft.com

Microsoft

huliao@microsoft.com

Nok Nok Labs

rolf@noknok.com

Yubico

emil@yubico.com

W3C Recommendation

Acknowledgements Thanks to , , , , , , , , , , , , , , , , , , , , and for their roles in registering these algorithm identifiers.

Author's Address Microsoft

mbj@microsoft.com https://self-issued.info/