
Pluggable Cryptographic Key Provider for DICOM De-Identification
Source:R/deid-keys.R
dicom_key_provider.RdManages cryptographic master keys, password-based key derivation (PBKDF2), domain-separated subkey expansion (HKDF-SHA256), and pluggable enterprise key broker/trusted-third-party (TTP) resolution.
Usage
dicom_key_provider(
mode = c("local", "broker", "ttp"),
key = NULL,
passphrase = NULL,
salt = NULL,
keyfile = NULL,
resolver_fn = NULL
)Arguments
- mode
Character string specifying key management mode:
"local"for local key derivation via PBKDF2/HKDF,"broker"for an enterprise cryptographic key broker callback,"ttp"for a trusted third party pseudonym resolution service.- key
Optional 32-byte raw vector containing a pre-shared master key.
- passphrase
Optional character string or raw vector containing a passphrase used to derive the master key via PBKDF2-HMAC-SHA256.
- salt
Optional character string or raw vector containing salt for PBKDF2. Defaults to an internal versioned salt if omitted.
- keyfile
Optional file path pointing to a binary file containing the 32-byte key.
- resolver_fn
Optional function callback used when
modeis"broker"or"ttp". Must accept a domain name string and return raw key bytes.
Details
Subkeys are stored in a private environment closure to ensure that secret key
bytes and passphrases are never leaked through print(), format(), or str().
Examples
kp <- dicom_key_provider(passphrase = "clinical-trial-secret", salt = "site-001")
is_dicom_key_provider(kp)
#> [1] TRUE
print(kp)
#> <dicom_key_provider: local [REDACTED]>
#> Status: active
#> Keys: <REDACTED>