Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TLS error #70

Closed
MikoyChinese opened this issue Dec 23, 2021 · 4 comments
Closed

TLS error #70

MikoyChinese opened this issue Dec 23, 2021 · 4 comments

Comments

@MikoyChinese
Copy link

when I run the lastest version, I got a tls error:

[INF] Thu, 23 Dec 2021 10:41:37 CST Sshwifty > Server (127.0.0.1:2222): Serving TLS
[WRN] Thu, 23 Dec 2021 10:41:37 CST Sshwifty > Server (127.0.0.1:2222): Failed to serve due to error: http2: TLSConfig.CipherSuites index 5 contains an HTTP/2-approved cipher suite (0x1301), but it comes after unapproved cipher suites. With this configuration, clients that don't support previous, approved cipher suites may be given an unapproved one and reject the connection.
[ERR] Thu, 23 Dec 2021 10:41:37 CST Sshwifty: Unable to start due to error: http2: TLSConfig.CipherSuites index 5 contains an HTTP/2-approved cipher suite (0x1301), but it comes after unapproved cipher suites. With this configuration, clients that don't support previous, approved cipher suites may be given an unapproved one and reject the connection.
[INF] Thu, 23 Dec 2021 10:41:37 CST Sshwifty: Closed
@nirui
Copy link
Owner

nirui commented Dec 23, 2021

Hmm... that's odd, it literally work on my machines.

Recently, I committed 5d4c387 which changed how TLS CipherSuites are selected, it has to be the cause. I'll revert that to the default, it should fix the problem.

Do you want me to create a new release to carry out this fix immediately? I could do that if you're in a hurry.

Sorry for the trouble.

nirui pushed a commit that referenced this issue Dec 23, 2021
@MikoyChinese
Copy link
Author

Emmm.. Maybe TLS CipherSuites in go 1.7+ no order anymore. But I don't know why start a ServeTLS will init a HTTP2.

@nirui
Copy link
Owner

nirui commented Dec 23, 2021

I've released 0.2.20-beta which includes the said changes, the new version should fix this issue. Please give it a try.

I'll close this issue for now. If the fix did not work as expected, feel free to re-open this issue and I'll investigate it further.

Thanks!

@nirui nirui closed this as completed Dec 23, 2021
@Abirdcfly
Copy link

This fix (committ 5d4c387 ) works fine with go1.17+.

The previous bug was fixed by golang/go#45430

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants