Skip to content

warning when TLS 1.3 only early key share group is configured but connection negotiates TLS 1.2 #2392

Description

@matthew-js-porter

When org.bouncycastle.jsse.client.earlyKeyShares includes X25519MLKEM768 and the connection negotiates TLS 1.2 (e.g. because the server is TLS 1.2-only). a warning is logged on every connection:

WARNING: Candidate early key share not an enabled named group: X25519MLKEM768

Should this be reduced to DEBUG (or suppressed entirely) when the group is only inactive due to the negotiated protocol version?

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