On Wed, Dec 28, 2005 at 12:30:53PM +0100, Javier Fernández-Sanguino Peña wrote:
> On Wed, Dec 28, 2005 at 03:12:44AM -0800, Steve Langasek wrote:
> > > Since there is no libssl097-dev any longer I guess I'll have to recompile
> > > all
> > > packages.
> > It should actually be possible to fix th
On Thu, Dec 29, 2005 at 11:17:41AM +0100, Marc Haber wrote:
> The resulting packages naturally only depend on libssl0.9.7, and seem
> to work fine. This might be a workaround.
Great, yes, this is a workaround. Unfortunately it's a *local* workaround.
Even if I can generate i386 packages compiled f
On Wed, Dec 28, 2005 at 10:57:42AM +0100, Javier Fernández-Sanguino Peña wrote:
> severity 343487 grave
> tags 343487 pending confirmed sid etch
> reassign 343487 nessus
> thanks
>
> I downgraded the nessus client version to 2.2.5-2 (which is *not* compiled
> against both 0.9.7 and 0.9.8 SSL libra
On Wed, Dec 28, 2005 at 02:54:17AM -0800, Steve Langasek wrote:
>
> > * nessusd 2.2.5-3, the server, is linked against both 0.9.7 and
> > 0.9.8
>
> Ok, I don't see this either:
>
> $ ldd /tmp/nessus/usr/sbin/nessusd|grep ssl
> libssl.so.0.9.8 => not found
> $
Funny, it seems that ldd ou
On Wed, Dec 28, 2005 at 03:12:44AM -0800, Steve Langasek wrote:
>
> > Since there is no libssl097-dev any longer I guess I'll have to recompile
> > all
> > packages.
>
> It should actually be possible to fix this with binNMUs on the autobuilders,
> I think. I'll go ahead and queue those now.
P
On Wed, Dec 28, 2005 at 11:59:14AM +0100, Javier Fernández-Sanguino Peña wrote:
> On Wed, Dec 28, 2005 at 11:31:11AM +0100, Javier Fernández-Sanguino Peña
> wrote:
> >
> > * nessusd 2.2.5-3, the server, is linked against both 0.9.7 and
> > 0.9.8
> Just found out why this happened. The Nessus ser
On Wed, Dec 28, 2005 at 11:31:11AM +0100, Javier Fernández-Sanguino Peña wrote:
>
> * nessusd 2.2.5-3, the server, is linked against both 0.9.7 and
> 0.9.8
Just found out why this happened. The Nessus server gets compile against
both versions since libnasl depends on 0.9.7, I did not notice this:
On Wed, Dec 28, 2005 at 11:31:11AM +0100, Javier Fernández-Sanguino Peña wrote:
> On Wed, Dec 28, 2005 at 02:16:26AM -0800, Steve Langasek wrote:
> > > The issue should be fixed by recompiling the client against a set of the
> > > libraries, and should affect only the 2.2.5-3 version under i386. No
On Wed, Dec 28, 2005 at 02:16:26AM -0800, Steve Langasek wrote:
> > The issue should be fixed by recompiling the client against a set of the
> > libraries, and should affect only the 2.2.5-3 version under i386. Notice,
> > also that the package has an undeclared dependency on libssl0.9.7 (the
> >
On Wed, Dec 28, 2005 at 10:57:42AM +0100, Javier Fernández-Sanguino Peña wrote:
> After debugging this issue in a system that Marc Haber set up for testing
> I've found two different issues, one is a misconfiguration, the other is a
> problem with the nessus package (the client)
> - (fixing the ab
On Thu, Dec 15, 2005 at 10:17:13PM +0100, Javier Fernández-Sanguino Peña wrote:
> On Thu, Dec 15, 2005 at 07:18:04PM +0100, Marc Haber wrote:
> > [2/[EMAIL PROTECTED] sid]:~$ md5sum nessusd_2.2.5-3_i386.deb
> > 5540b1f4dfd81c4ba3c71ac4e2dbecfa nessusd_2.2.5-3_i386.deb
> > [3/[EMAIL PROTECTED] sid]
On Thu, Dec 15, 2005 at 07:18:04PM +0100, Marc Haber wrote:
> [2/[EMAIL PROTECTED] sid]:~$ md5sum nessusd_2.2.5-3_i386.deb
> 5540b1f4dfd81c4ba3c71ac4e2dbecfa nessusd_2.2.5-3_i386.deb
> [3/[EMAIL PROTECTED] sid]:~$
That is correct, however, with that one, as I said:
$ ldd /usr/sbin/nessusd |grep
On Thu, Dec 15, 2005 at 07:00:05PM +0100, Javier Fernández-Sanguino Peña wrote:
> On Thu, Dec 15, 2005 at 06:44:18PM +0100, Marc Haber wrote:
> > > libssl.so.0.9.8 => /usr/lib/i686/cmov/libssl.so.0.9.8 (0x40115000)
> > > libssl.so.0.9.7 => /usr/lib/i686/cmov/libssl.so.0.9.7 (0x403b4
On Thu, Dec 15, 2005 at 06:44:18PM +0100, Marc Haber wrote:
> > libssl.so.0.9.8 => /usr/lib/i686/cmov/libssl.so.0.9.8 (0x40115000)
> > libssl.so.0.9.7 => /usr/lib/i686/cmov/libssl.so.0.9.7 (0x403b4000)
>
> NACK.
Err... Is this i386 or some other arch?
Those are *not* the binaries
On Thu, Dec 15, 2005 at 06:20:01PM +0100, Javier Fernández-Sanguino Peña wrote:
> On Thu, Dec 15, 2005 at 05:17:36PM +0100, Marc Haber wrote:
> > A recompiled 2.2.5-3 on current sid exhibit the same behavior.
> >
> > I suspect some library issue.
>
> Yes, that looks like an SSL error due to incom
On Thu, Dec 15, 2005 at 05:17:36PM +0100, Marc Haber wrote:
> Package: nessusd
> Version: 2.2.5-3
> Severity: important
>
> When I try to connect to a 2.2.5-3 server from a 2.2.5-2 or 2.2.5-3
> client, the client says after hitting the "Login" button "SSL Error"
> and says on stdout "[8157] SSL_co
Package: nessusd
Version: 2.2.5-3
Severity: important
When I try to connect to a 2.2.5-3 server from a 2.2.5-2 or 2.2.5-3
client, the client says after hitting the "Login" button "SSL Error"
and says on stdout "[8157] SSL_connect: error:140943FC:SSL
routines:SSL3_READ_BYTES:sslv3 alert bad record
17 matches
Mail list logo
