Skip to content

TransportServices needs a mechanism for cert reloading #140

Description

@wrinkl3

Currently, if we create a long-running client backed by TS-transport against a short-lived cert, there's no clear mechanism to ensure that the client picks up a new cert once the initial one expires. POSIX-backed transport solves this with CertificateReloader, TS should either implement something similar or give the callers the ability to pass a closure for sec_protocol_options_set_challenge_block.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions