]> Bundesdruckerei GmbH

bastianpaul@googlemail.com

Bundesdruckerei GmbH

kraus.micha@gmail.com

IDsec Solutions

stefan@aaa-sec.com

The Agency for Digital Government

altmann@mail.com

Security Javascript Object Signing and Encryption JOSE JWS designated verifier signature This specification defines structures and algorithm descriptions for the use of designated verifier signatures, based on a combination of Key Agreement and Message Authentication Code, with JOSE. About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the Javascript Object Signing and Encryption Working Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .

Introduction Designated verifier signatures (DVS) are signature schemes in which signatures are generated, that can only be verified by a particular party. Unlike conventional digital signature schemes like ECDSA, this enables repudiable signatures. This specification describes a general structure for designated verifier signature schemes and specified a set of instantiations that use a combination of an KA-DH (Diffie-Hellman key aggrement) with an MAC (Message Authentication Code algorithm). The combination of ECKA-DH and MAC is a established mechanism and used, for example, in the mobile driving licence (mDL) application, specified in . This specification and all described algorithms should respect the efforts for Fully Specified Algorithms. This algorithm is intended for use with digital credentials ecosystems, including the Issuer-Holder-Verifier model described by W3C VCDM or IETF SD-JWT-VC.

Conventions and Definitions 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.

Terminology The draft uses "JSON Web Signature", "JOSE Header", "JWS Signature", "JWS Signing Input" as defined by .

Signing Party:

The Party that performs the key agreement first and generates the MAC. Similar to a Signer.

Verifying Party:

The Party that performs the key agreement second, generates the MAC and compares it to a given value. Similar to a Verifier.

Cryptographic Dependencies DVS rely on the following primitives:

• A Diffie-Hellman Key Agreement (KA-DH), for example ECKA-DH defined in :
  • DH(skX, pkY): Perform a non-interactive Diffie-Hellman exchange using the private key skX and public key pkY to produce a Diffie-Hellman shared secret of length Ndh. This function can raise a ValidationError.
  • Ndh: The length in bytes of a Diffie-Hellman shared secret produced by DH().
  • Nsk: The length in bytes of a Diffie-Hellman private key.
• A key derivation function (KDF), for example HKDF defined in :
  • Extract(salt, ikm): Extract a pseudorandom key of fixed length Nh bytes from input keying material ikm and an optional byte string salt.
  • Expand(prk, info, L): Expand a pseudorandom key prk using optional string info into L bytes of output keying material.
  • Nh: The output size of the Extract() function in bytes.
• A Message Authentication Code algorithm (MAC), for example HMAC defined in :
  • MacSign(k, i): Returns an authenticated tag for the given input i and key k.
  • Nk: The length in bytes of key k.

Designated Verifier Signatures A designated verifier signature requires three components for an algorithm:

1. a Diffie-Hellman Key Agreement (DHKA)
2. a Key Derivation Function (KDF)
3. a Message Authentication Code algorithm (MAC)

In general, these parameters are chosen by the Signing Party. These parameters need to be communicated to the Verifying Party before the generation of a Designated Verifier Signature.

Signature Generation The generation of the Designated Verifier Signature takes the private key of the Signing Party, the public key of the Verifying Party and the message as inputs. The retrieval and communication of the Verifying Party's public key is out of scope of this specification and subject to the implementing protocols. Input:

• skS: private key of the Signing Party
• pkR: public key of the Verifying Party
• msg: JWS Signing Input
• salt : Salt for key derivation
• info : optional info for key derivation

Function:

Signature Verification The generation of the Designated Verifier Signature takes the private key of the Signing Party, the public key of the Verifying Party and the message as inputs. The retrieval and communication of the Verifying Party's public key is out of scope of this specification and subject to the implementing protocols. Input:

• skR: private key of the Verifying Party
• pkS: public key of the Signing Party
• msg: JWS Signing Input
• salt : Salt for key derivation
• info : optional info for key derivation
• signature : the Message Authentication Code

Function:

Signature Suites Algorithms MUST follow the naming DVS-<DHKA>-<KDF>-<MAC>.

Designated Verifier Signatures for JOSE Designated Verifier Signatures behave like a digital signature as described in Section 3 of and are intended for use in JSON Web Signatures (JWS) as described in . The Generating Party performs the Message Signature or MAC Computation as defined by Section 5.1 of . The Verifying Party performs the Message Signature or MAC Validation as defined by Section 5.2 of . The following JWS headers are used to convey Designated Verifier Signatures for JOSE:

• alg : REQUIRED. The algorithm parameter describes the chosen signature suite, for example the ones described in (#generic_suites).
• rpk : REQUIRED. The rpk (recipient public key) parameter represents the encoded public key of the Verifying Party that was used in the DHKA algorithm as a JSON Web Key according to . This parameter MUST be present.
• nonce : OPTIONAL. The nonce may be provided by the Verifying Party additional to it's public key and ensure additional freshness of the signature. If provided, the Signing Party SHOULD add the nonce to the header.

The Signing Party may use existing JWS header parameters like x5c, jwk or kid to represent or reference it's public key according to .

Example JWT The JWT/JWS header: , "rpk" : } ]]> The JWT/JWS payload: The JWT/JWS signature: This specification described instantiations of Designated Verifier Signatures using specific algorithm combinations:

Security Considerations

Replay Attack Detection Verifying party MUST ensure the freshness of signatures by utilizing ephemeral keys in rpk or by providing a nonce for nonce.

Limited Repudiability A malicious verifiying party can weaken the repudiability property by involving certain third parties in the protocol steps.

• One method is to have a third party observe all protocol steps so that third party can be sure that the signature originates by the signer.
• Another method requires that the verifying party's public key is a shared key that has previously been calculated with the keys of certain specific third parties so that the proof of authenticity can be done with Multi Party Computation involving all parties (see ).

IANA Considerations Define:

• define new rpk header parameter
• alg values for DVS-P256-SHA256-HS256 and some more

References Normative References 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 describes a scheme for hybrid public key encryption (HPKE). This scheme provides a variant of public key encryption of arbitrary-sized plaintexts for a recipient public key. It also includes three authenticated variants, including one that authenticates possession of a pre-shared key and two optional ones that authenticate possession of a key encapsulation mechanism (KEM) private key. HPKE works for any combination of an asymmetric KEM, key derivation function (KDF), and authenticated encryption with additional data (AEAD) encryption function. Some authenticated variants may not be supported by all KEMs. We provide instantiations of the scheme using widely used and efficient primitives, such as Elliptic Curve Diffie-Hellman (ECDH) key agreement, HMAC-based key derivation function (HKDF), and SHA2. This document is a product of the Crypto Forum Research Group (CFRG) in the IRTF. This document specifies a simple Hashed Message Authentication Code (HMAC)-based key derivation function (HKDF), which can be used as a building block in various protocols and applications. The key derivation function (KDF) is intended to support a wide range of applications and requirements, and is conservative in its use of cryptographic hash functions. This document is not an Internet Standards Track specification; it is published for informational purposes. This document describes HMAC, a mechanism for message authentication using cryptographic hash functions. HMAC can be used with any iterative cryptographic hash function, e.g., MD5, SHA-1, in combination with a secret shared key. The cryptographic strength of HMAC depends on the properties of the underlying hash function. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind 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. 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. Informative References

Acknowledgments Thanks to:

• Brian Campbell
• John Bradley