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.

Sign up for GitHub

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

Jump to bottom

Fails to build with OpenSSL 1.1.1 #4

Closed
sebastic opened this issue Aug 23, 2018 · 0 comments
Closed

Fails to build with OpenSSL 1.1.1 #4

sebastic opened this issue Aug 23, 2018 · 0 comments

Comments

@sebastic
Copy link

As reported by Sebastian Andrzej Siewior in Debian Bug #900152:

The new openssl 1.1.1 is currently in experimental [0]. This package
failed to build against this new package [1] while it built fine against
the openssl version currently in unstable [2].
Could you please have a look?

The Error in the testsuite could be due to:
1.1.1~~pre6-1 changelog):

  • Increase default security level from 1 to 2. This moves from the 80 bit
    security level to the 112 bit securit level and will require 2048 bit RSA
    and DHE keys.

[0] https://lists.debian.org/msgid-search/20180501211400.GA21460@roeckx.be
[1] https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/attempted/nsca-ng_1.5-2_amd64-2018-05-01T20%3A31%3A09Z
[2] https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/successful/nsca-ng_1.5-2_amd64-2018-05-02T18%3A46%3A37Z

The issue can be reproduced in Debian unstable where openssl (1.1.1~~pre9-1) is now available.

Full buildlog: nsca-ng_1.5-4_amd64.txt

Testsuite log: nsca-ng_1.5-4_amd64_testsuite.txt
@weiss weiss closed this as completed in 7d9ca34 Mar 19, 2019
weiss added a commit that referenced this issue Mar 19, 2019
@weiss
Work around TLSv1.3 PSK bug in OpenSSL 1.1.1
d197afc 
When TLSv1.3 is used with (at least) OpenSSL 1.1.1b, the
SSL_get_psk_identity(3) unexpectedly returns NULL.  Work around this
issue by storing a copy of the PSK identity into the SSL object.

Closes #4.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sebastic