Skip to content

doc: which traits must be implemented for a custom crypto provider #1603

@jsha

Description

@jsha

I was looking up how to implement a custom crypto provider. It looks like it's not currently documented in a consolidated place. These are all the traits found in modules under rustls::crypto, plus some in rustls::quic. Could someone confirm whether this is the full set? Also, does each provider need to implement all of the ones not marked Optional, or is it expected that some providers would delegate to an existing default implementation for some of them?

Optional: QUIC

Optional: HPKE

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions