This paragraph describes the technical format of key file provided to Dienstverleners (Service Providers).
Formats of cryptographic keys provided to Service Providers
Parties that are provided with either Encrypted Identities or Encrypted Pseudonyms are also provided cryptographic keys to decrypt them to respectively Identities or Pseudonyms. These cryptographic keys are provided as ECPrivateKey as specified in RFC5915, in files formatted according to the PEM specifications (RFC1421).
Encrypted key format
Each key(file) containing one DV-key will be provided in an encrypted form, to protect the key from disclosure during the provisioning. The encryption is in CMS as per RFC5652. This format is typically used in PEM or S/MIME format.
The encryption has the following charcteristics:
- Hybrid encryption, using a new random symmetric key per encrypted DV-key-file
- AES-256 in CBC-mode for symmetric encryption
- the AES key is encrypted to the DV with RSA encryption, using the RSA public key from the PKIoverheid certificate in the request.
- This results in 'keyTransport' in CMS for protection of the content-encryption key.
- the CMS reference the Issuer and SerialNumber of the DV-certificate
The structure of the CMS is:
|field||value / comment|
|version||0 (fixed, as per RFC5652)|
|recipientInfos||1 RecipientInfo for the receiver (DV)|
|...recipientInfo||van het type KeyTransportRecipientInfo|
|......version||0 (fixed, as per RFC5652)|
|.........Issuer||copy of DV certificate (via Interface spec BSNk: provideDVKeys)|
|.........Serial||copy of DV certifcate (via Interface spec BSNk: provideDVKeys)|
1.2.840.1135126.96.36.199 = rsaOAEP (as per RFC3447?)
|.........hashAlgorithm||2.16.8188.8.131.52.4.2.1 = SHA-256 as hash function for OAEP|
|.........maskGenAlgorithm||1.2.840.1135184.108.40.206 = PKCS#1 MGF as mask function for OAEP|
|.........pSourceAlgorithm||2.16.8220.127.116.11.4.2.1 = SHA-256 as digest for the mask function for OAEP|
|......key||the AES content-encryption key encrypted with RSA-OAEP to the above referenced certificate|
|1.2.840.113518.104.22.168 = data (PKCS #7)|
2.16.822.214.171.124.4.1.42 = aes256-CBC (NIST Algorithm, as per RFC3565)
|......iv||16-byte octet string, the IV for the AES encryption|
|......encryptedContent||the PEM-encoded content (DV PP-key as described below), encrypted with AES-256-CBC using the content-encryption key included above.|
This can be created using openssl:
This can be decrypted using openssl:
Key file format
The actual cryptographic keys obtained after decryption, have the format described below.
As per RFC5915 (section 4), all DV-key files contain a EC private key object, using the PEM-encoding of the DER-encoded ECPrivateKey structure. The actual key is preceded by the line
and followed with the line
These headers use a 'key: value' notation, as specified in RFC1421. Applicable headers MUST be present for a given keytype, unless stated otherwise,
|Header name||Meaning||Applicable to keytypes|
|Scheme version (see also 2d. Polymorphic Pseudonymization Notation.)||All|
|SchemeKeySetVersion (see also 2d. Polymorphic Pseudonymization Notation.)||All|
|OIN of the recipient. (Service Provider) (see also 2d. Polymorphic Pseudonymization Notation.)|
|RecipientKeySetVersion for a Service Provider corresponds with the issue date of the PKIoverheid certificate used to request their keys at the party generating the keys within the scheme. The RecipientKeySetVersion will therefore be an 8-digit decimal representation of a date in the YYYYMMDD format. (see also 2d. Polymorphic Pseudonymization Notation.)|
MUST have one of the following values (case-sensitive):
|Source OIN in migration||EP Migration|
|RecipientKeySetVersion of the closing key used at source||EP Migration|
|Target OIN in migration||EP Migration|
|RecipientKeySetVersion of the closing key used at target||EP Migration|
ID of the migration (for identification purpose, can be used to match source and target keys)
Type: String, MUST only contain characters (A-F)(0-9) and '-', minimum length =1
Optional Value of diversifier. Comma-separated list of key-value pairs. Keys and values separated by '='
|(Deprecated) Alias for ||All|
EC private key format
The key is a ECPrivateKey, defined by
thus consisting of 4 elements:
- a version (integer of value 1),
- an OCTET STRING corresponding to the actual private key (40 bytes)
- a tagged OBJECT IDENTIFIER of value 126.96.36.199.188.8.131.52.1.9 indicating the BrainpoolP320r1 curve.
- a tagged BIT STRING representing the corresponding public key (an EC point, uncompressed).
In line with RFC5915, both the curve name and the public key will be provided, even though these are indicated as optional.
We remark that the following OpenSSL (version 1.0.2) command will provide a PEM file corresponding to the above specification without the headers:
and key files can be read by the command
The confidentiality and authenticity of the key files in transport to the intended parties is required but not further specified. On receipt of a PEM file the intended party MUST validate that the PEM is correctly formed which also includes that the provided private key and public key match. That is, if x represents this private key and G the BrainpoolP320r1 generator, then the intended party needs to validate that x*G is equal to the public key in the key file. The recipient furthermore MUST ensure each key is adequately secured against disclosure or abuse.
Note: OpenSSL PEM_read function (https://www.openssl.org/docs/man1.1.0/crypto/PEM_read.html) supports this format.