EdhocResponderConfig

class EdhocResponderConfig(methods: Set<EdhocMethod>, cipherSuites: List<CipherSuite>, credentials: List<LocalCredential>, val credentialResolver: CredentialResolver, val connectionIdentifiers: ConnectionIdentifierProvider = ConnectionIdentifierProvider.Random, val eadHandler: EadHandler = EadHandler.None, val ephemeralKeys: EphemeralKeySource = EphemeralKeySource.Random)(source)

The application profile (RFC 9528 §3.9) of an EdhocResponder.

Constructors

Link copied to clipboard
constructor(methods: Set<EdhocMethod>, cipherSuites: List<CipherSuite>, credentials: List<LocalCredential>, credentialResolver: CredentialResolver, connectionIdentifiers: ConnectionIdentifierProvider = ConnectionIdentifierProvider.Random, eadHandler: EadHandler = EadHandler.None, ephemeralKeys: EphemeralKeySource = EphemeralKeySource.Random)

Properties

Link copied to clipboard

the supported suites. Only those the crypto backend runs for the received method (CipherSuite.isSupportedBy) are accepted and named in SUITES_R, where their order has no meaning (RFC 9528 §6.3). supportedBy narrows the list to them up front.

Link copied to clipboard
Link copied to clipboard

resolves and authorizes ID_CRED_I.

Link copied to clipboard

own credentials; the first one usable for the received method and suite is used.

Link copied to clipboard
Link copied to clipboard

source of Y on Diffie-Hellman suites.

Link copied to clipboard

the methods the Responder accepts.

Functions

Link copied to clipboard

This configuration with only the cipher suites crypto runs for at least one of methods with a credential (CipherSuite.isSupportedBy, docs/adr/0001-crypto-capabilities.md). EdhocResponder makes the same choice, per method, when it processes message_1, so SUITES_R names only runnable suites and a selected suite it cannot run gets error code 2 (RFC 9528 §6.3). Both ask the backend once per configuration and remember the answers; the returned configuration keeps them for crypto, so no message_1 makes the backend answer again. Calling this once where the configuration is set up finds a backend that cannot run it before any session starts.

Link copied to clipboard

This configuration with C_R chosen by connectionIdentifiers, for example by a server that allocates C_R per session. What it learnt of crypto backends (supportedBy, earlier sessions) is shared with the copy, so a copy per session does not ask the backend again.