Bug#499945: Segfault in asn1_get_tag_der().
simon at josefsson.org
Thu Sep 25 07:56:58 UTC 2008
Kurt Roeckx <kurt at roeckx.be> writes:
> On Wed, Sep 24, 2008 at 08:05:24PM +0200, Andreas Metzler wrote:
>> On 2008-09-23 Kurt Roeckx <kurt at roeckx.be> wrote:
>> > Package: libtasn1-3
>> > Version: 1.4-1
>> > Severity: grave
>> > When I run "lynx https://acrobat.com", I end up with a segfault. The
>> > backtrace looks like:
>> > I'm running libgnutls26 2.4.1-1 and lynx-cur 2.8.7dev9-2.
>> FWIW I get the same behavior Simon describes ("SSL error:no issuer was
>> found-Continue? (y)" followed by "Alert!: Unexpected network read
>> error; connection aborted.") *both* on ix86 and amd64 (the latter on
>> pergolesi.d.o's unstable_amd64 chroot), using the same versions of
>> libgnutls26 and lynx-cur.
>> Have you got any special settings in ~/lynxrc?
> No, it's the default setting.
> But it seems to be related to me using MALLOC_CHECK_=2 in the
> enviroment. I thought I've set it to 0 to make sure it wasn't
> related. But trying to unset or set it to 0 now stops the segfault.
> Also not that the check even with set to 3 it doesn't print any error
I can't reproduce this on an x86 with MALLOC_CHECK_=2, but maybe it
requires an amd64 platform. Btw, which libc6 verison do you use? I use
Btw, openssl's way of saying that the other end disconnected improperly
appears to be to print 'read:errno=0'. This is the same as the GnuTLS
error about a packet of unexpected length (i.e., packet size 0).
More information about the Pkg-gnutls-maint