Bug#900152: nsca-ng: FTBFS against openssl 1.1.1

2019-03-20 Thread Holger Weiß
* Kurt Roeckx [2019-03-20 07:31]: > On Tue, Mar 19, 2019 at 11:21:19PM +0100, Holger Weiß wrote: > > * Kurt Roeckx [2019-03-19 22:59]: > > > On Tue, Mar 19, 2019 at 10:28:06PM +0100, Holger Weiß wrote: > > > > Yes, it's an OpenSSL bug. If TLSv1.3 is used, SSL_get_psk_identity()¹ > > > > unexpect

Bug#900152: nsca-ng: FTBFS against openssl 1.1.1

2019-03-19 Thread Kurt Roeckx
On Tue, Mar 19, 2019 at 11:21:19PM +0100, Holger Weiß wrote: > * Kurt Roeckx [2019-03-19 22:59]: > > On Tue, Mar 19, 2019 at 10:28:06PM +0100, Holger Weiß wrote: > > > Yes, it's an OpenSSL bug. If TLSv1.3 is used, SSL_get_psk_identity()¹ > > > unexpectedly returns NULL. I now avoid the function

Bug#900152: nsca-ng: FTBFS against openssl 1.1.1

2019-03-19 Thread Holger Weiß
* Kurt Roeckx [2019-03-19 22:59]: > On Tue, Mar 19, 2019 at 10:28:06PM +0100, Holger Weiß wrote: > > Yes, it's an OpenSSL bug. If TLSv1.3 is used, SSL_get_psk_identity()¹ > > unexpectedly returns NULL. I now avoid the function to work around the > > issue. > > This is documented here: > https:/

Bug#900152: nsca-ng: FTBFS against openssl 1.1.1

2019-03-19 Thread Kurt Roeckx
On Tue, Mar 19, 2019 at 10:28:06PM +0100, Holger Weiß wrote: > Just for the record: > > * Sebastian Andrzej Siewior [2018-11-05 00:28]: > > It is a TLS1.3 issue. If I limit max protocol to TLS1.2 then the > > testsuite passes. > > Yes, it's an OpenSSL bug. If TLSv1.3 is used, SSL_get_psk_identi

Bug#900152: nsca-ng: FTBFS against openssl 1.1.1

2019-03-19 Thread Holger Weiß
Just for the record: * Sebastian Andrzej Siewior [2018-11-05 00:28]: > It is a TLS1.3 issue. If I limit max protocol to TLS1.2 then the > testsuite passes. Yes, it's an OpenSSL bug. If TLSv1.3 is used, SSL_get_psk_identity()¹ unexpectedly returns NULL. I now avoid the function to work around t

Bug#900152: nsca-ng: FTBFS against openssl 1.1.1

2018-11-04 Thread Kurt Roeckx
On Mon, Nov 05, 2018 at 12:28:50AM +0100, Sebastian Andrzej Siewior wrote: > > No, it is not. It is a TLS1.3 issue. If I limit max protocol to TLS1.2 > then the testsuite passes. The problem with TLS1.3 could be that > SSL_read() could return SSL_ERROR_WANT_READ asking to do the same. Was > there

Bug#900152: nsca-ng: FTBFS against openssl 1.1.1

2018-11-04 Thread Sebastian Andrzej Siewior
On 2018-05-26 23:35:46 [+0200], To sub...@bugs.debian.org wrote: > 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 >

Bug#900152: nsca-ng: FTBFS against openssl 1.1.1

2018-08-23 Thread Holger Weiß
* Sebastiaan Couwenberg [2018-08-23 07:13]: > Are you aware of this issue in NSCA-ng? No. > I did not find a link to a bugtracker on nsca-ng.org, so I'm forwarding > this by email. I've now enabled the issue tracker on GitHub; if you believe this to be an upstream bug, feel free to report it th

Bug#900152: nsca-ng: FTBFS against openssl 1.1.1

2018-08-22 Thread Sebastiaan Couwenberg
Hi Holger, Are you aware of this issue in NSCA-ng? I did not find a link to a bugtracker on nsca-ng.org, so I'm forwarding this by email. On Sat, 26 May 2018 23:35:46 +0200 Sebastian Andrzej Siewior wrote: > Source: nsca-ng > Version: 1.5-2 > Severity: important > User: pkg-openssl-de...@lists.a