Bug#846113: polygraph loses SSL support when compiled with OpenSSL 1.1

2016-11-30 Thread Adrian Bunk
On Wed, Nov 30, 2016 at 09:43:48PM +0100, Sebastian Andrzej Siewior wrote: > On 2016-11-30 01:16:09 [+0200], Adrian Bunk wrote: > > > I though we agreed not to tag this as a patch > > > > Where did I agree to that? > > The last time I pointed it out and you replied that the problem is that > "two

Bug#846113: polygraph loses SSL support when compiled with OpenSSL 1.1

2016-11-30 Thread Sebastian Andrzej Siewior
On 2016-11-30 01:16:09 [+0200], Adrian Bunk wrote: > > I though we agreed not to tag this as a patch > > Where did I agree to that? The last time I pointed it out and you replied that the problem is that "two things are tracked in one bug but it can't be cloned". > > but as a hint what can be >

Bug#846113: polygraph loses SSL support when compiled with OpenSSL 1.1

2016-11-29 Thread Adrian Bunk
On Tue, Nov 29, 2016 at 11:50:21PM +0100, Sebastian Andrzej Siewior wrote: > On 2016-11-28 16:49:35 [+0200], Adrian Bunk wrote: > > Package: polygraph > > Version: 4.3.2-4 > > Severity: serious > > Tags: patch > > Control: block 827061 by -1 > > > > ... > > checking for CRYPTO_lock in -lcrypto...

Bug#846113: polygraph loses SSL support when compiled with OpenSSL 1.1

2016-11-29 Thread Sebastian Andrzej Siewior
On 2016-11-28 16:49:35 [+0200], Adrian Bunk wrote: > Package: polygraph > Version: 4.3.2-4 > Severity: serious > Tags: patch > Control: block 827061 by -1 > > ... > checking for CRYPTO_lock in -lcrypto... no > checking for CRYPTO_add_lock in -lcrypto... no > ... > > Not a perfect solution but an

Bug#846113: polygraph loses SSL support when compiled with OpenSSL 1.1

2016-11-28 Thread Adrian Bunk
Package: polygraph Version: 4.3.2-4 Severity: serious Tags: patch Control: block 827061 by -1 ... checking for CRYPTO_lock in -lcrypto... no checking for CRYPTO_add_lock in -lcrypto... no ... Not a perfect solution but an option for stretch is the patch below to use OpenSSL 1.0.2 The "| libssl-