Bug#828556: sslscan: FTBFS with openssl 1.1.0

2017-01-06 Thread Sebastian Andrzej Siewior
On 2017-01-05 23:33:59 [+0100], Christoph Berg wrote:
> > why on libssl-dev (<< 1.1.0~)?
> 
> The | libssl-dev (<< 1.1.0~) part is there to enable backporting to
> jessie without having to revert libssl1.0-dev back to libssl-dev.

and I though that this is one of the changes you do when you intend to
backport a package. But now looking at some other packages I see that
more people did this :/ So I need to fix my tracker…

> > Otherwise I'm fine with it. I asked the release team & security if they
> > object adding openssl's source to sslscan and the release was not too
> > happy about it. With latest libssl1.0 upload sslscan won't be able to
> > detect 3des ciphers…
> 
> I guess with openssl 1.1 that would also be the case so it doesn't
> make a difference.

Yes. I did not imply to convert to 1.1 I just tried to point out some of
the limitations…

> Christoph

Sebastian



Bug#828556: sslscan: FTBFS with openssl 1.1.0

2017-01-05 Thread Christoph Berg
Re: Sebastian Andrzej Siewior 2017-01-05 
<20170105203350.67bp6zhioblxu...@breakpoint.cc>
> On 2017-01-05 15:08:00 [+0100], Christoph Berg wrote:
> > NMU diff:
> > 
> > 
> > Control files: lines which differ (wdiff format)
> > 
> > Build-Depends: debhelper (>= 9), {+libssl1.0-dev |+} libssl-dev {+(<< 
> > 1.1.0~)+}
> 
> why on libssl-dev (<< 1.1.0~)?

The | libssl-dev (<< 1.1.0~) part is there to enable backporting to
jessie without having to revert libssl1.0-dev back to libssl-dev.

> Otherwise I'm fine with it. I asked the release team & security if they
> object adding openssl's source to sslscan and the release was not too
> happy about it. With latest libssl1.0 upload sslscan won't be able to
> detect 3des ciphers…

I guess with openssl 1.1 that would also be the case so it doesn't
make a difference.

Christoph



Bug#828556: sslscan: FTBFS with openssl 1.1.0

2017-01-05 Thread Sebastian Andrzej Siewior
On 2017-01-05 15:08:00 [+0100], Christoph Berg wrote:
> NMU diff:
> 
> 
> Control files: lines which differ (wdiff format)
> 
> Build-Depends: debhelper (>= 9), {+libssl1.0-dev |+} libssl-dev {+(<< 
> 1.1.0~)+}

why on libssl-dev (<< 1.1.0~)?

Otherwise I'm fine with it. I asked the release team & security if they
object adding openssl's source to sslscan and the release was not too
happy about it. With latest libssl1.0 upload sslscan won't be able to
detect 3des ciphers…

> Christoph

Sebastian



Bug#828556: sslscan: FTBFS with openssl 1.1.0

2017-01-05 Thread Christoph Berg
Re: Adrian Bunk 2016-12-21 <20161221212734.64mvgghokxot7...@bunk.spdns.de>
> On Wed, Nov 30, 2016 at 04:53:58PM +0100, Marvin Stark wrote:
> > Am 2016-11-10 23:33, schrieb Sebastian Andrzej Siewior:
> >...
> > > Marvin: unless Adrian pulls out a patch I suggest you prepare a package
> > > to build against libssl1.0-dev. I have currently no better suggestion. I
> > > can sponsor the upload if you want me to.
> > 
> > Yes please. I'll prepare a new package these days.
> 
> ping

NMU diff:


Control files: lines which differ (wdiff format)

Build-Depends: debhelper (>= 9), {+libssl1.0-dev |+} libssl-dev {+(<< 1.1.0~)+}

diff -Nru sslscan-1.11.5-rbsec/debian/changelog 
sslscan-1.11.5-rbsec/debian/changelog
--- sslscan-1.11.5-rbsec/debian/changelog   2016-04-01 10:33:03.0 
+0200
+++ sslscan-1.11.5-rbsec/debian/changelog   2017-01-05 15:02:51.0 
+0100
@@ -1,3 +1,10 @@
+sslscan (1.11.5-rbsec-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build against openssl 1.0. (Closes: #828556)
+
+ -- Christoph Berg   Thu, 05 Jan 2017 15:02:51 +0100
+
 sslscan (1.11.5-rbsec-1) unstable; urgency=medium
 
   * New Upstream release (Closes: #804616)
diff -Nru sslscan-1.11.5-rbsec/debian/control 
sslscan-1.11.5-rbsec/debian/control
--- sslscan-1.11.5-rbsec/debian/control 2016-04-01 10:33:03.0 +0200
+++ sslscan-1.11.5-rbsec/debian/control 2017-01-05 15:02:51.0 +0100
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Marvin Stark 
 Homepage: https://github.com/rbsec/sslscan
-Build-Depends: debhelper (>= 9), libssl-dev
+Build-Depends: debhelper (>= 9), libssl1.0-dev | libssl-dev (<< 1.1.0~)
 Standards-Version: 3.9.7.0
 
 Package: sslscan


Christoph


signature.asc
Description: PGP signature


Bug#828556: sslscan: FTBFS with openssl 1.1.0

2016-11-30 Thread Marvin Stark

Am 2016-11-10 23:33, schrieb Sebastian Andrzej Siewior:

On 2016-11-10 12:10:04 [+0200], Adrian Bunk wrote:
On Thu, Sep 01, 2016 at 09:55:46PM +0200, Sebastian Andrzej Siewior 
wrote:

> control: forwarded -1 https://github.com/rbsec/sslscan/issues/108

Sebastian, Marvin, what is the status regarding getting this patch 
that

was applied upstream included in Debian?


Adrian: which patch?
Marvin: unless Adrian pulls out a patch I suggest you prepare a package
to build against libssl1.0-dev. I have currently no better suggestion. 
I

can sponsor the upload if you want me to.


Yes please. I'll prepare a new package these days.

--
 .""`. Marvin Stark 
: :"  :Homepage: www.der-marv.de
`. `"`
  `-  Debian - when you have better things to do than fix a system



Bug#828556: sslscan: FTBFS with openssl 1.1.0

2016-11-11 Thread Adrian Bunk
On Thu, Nov 10, 2016 at 11:33:40PM +0100, Sebastian Andrzej Siewior wrote:
> On 2016-11-10 12:10:04 [+0200], Adrian Bunk wrote:
> > On Thu, Sep 01, 2016 at 09:55:46PM +0200, Sebastian Andrzej Siewior wrote:
> > > control: forwarded -1 https://github.com/rbsec/sslscan/issues/108
> > 
> > Sebastian, Marvin, what is the status regarding getting this patch that 
> > was applied upstream included in Debian?
> 
> Adrian: which patch?
>...

I was mislead by
  Added tag(s) fixed-upstream. Request was from 
bts-link-upstr...@lists.alioth.debian.org to cont...@bugs.debian.org. (Thu, 08 
Sep 2016 17:43:06 GMT)
and didn't check that myself.

Sorry for the confusion.

> Sebastian

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed



Bug#828556: sslscan: FTBFS with openssl 1.1.0

2016-11-10 Thread Sebastian Andrzej Siewior
On 2016-11-10 12:10:04 [+0200], Adrian Bunk wrote:
> On Thu, Sep 01, 2016 at 09:55:46PM +0200, Sebastian Andrzej Siewior wrote:
> > control: forwarded -1 https://github.com/rbsec/sslscan/issues/108
> 
> Sebastian, Marvin, what is the status regarding getting this patch that 
> was applied upstream included in Debian?

Adrian: which patch?
Marvin: unless Adrian pulls out a patch I suggest you prepare a package
to build against libssl1.0-dev. I have currently no better suggestion. I
can sponsor the upload if you want me to.

> Thanks
> Adrian

Sebastian



Bug#828556: sslscan: FTBFS with openssl 1.1.0

2016-11-10 Thread Adrian Bunk
On Thu, Sep 01, 2016 at 09:55:46PM +0200, Sebastian Andrzej Siewior wrote:
> control: forwarded -1 https://github.com/rbsec/sslscan/issues/108

Sebastian, Marvin, what is the status regarding getting this patch that 
was applied upstream included in Debian?

Thanks
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed



Bug#828556: sslscan: FTBFS with openssl 1.1.0

2016-09-01 Thread Sebastian Andrzej Siewior
control: forwarded -1 https://github.com/rbsec/sslscan/issues/108



Bug#828556: sslscan: FTBFS with openssl 1.1.0

2016-06-26 Thread Kurt Roeckx
Source: sslscan
Version: 1.11.5-rbsec-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/sslscan_1.11.5-rbsec-1_amd64-20160529-1539

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt