Skip to content

Should also list the TLS clients that implement post-quantum algorithm by default #15

@thomvaill

Description

@thomvaill

Hi,

I finally was able to end my 3 days of debug when I found your website, thank you!! Very helpful.

I encountered this bug when upgrading our app from Go 1.22 to Go 1.23, which was communicating with a legacy SMTP server that does not handle TLS correctly.
After a lot of debug and this helpful comment on my issue: golang/go#71257 (comment) I was able to find out why.

Therefore I think it would be helpful to add the list of TLS clients (every programing language) that implement these post-quantum algorithms by default, like you did for the browsers.
Because especially in enterprise environment when there are often legacy services running, this problem will happen very often in the future.

What do you think?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions