#168840 w3m: Error message for invalid certificate files is too cryptic

Package:
w3m
Source:
w3m
Description:
WWW browsable pager with excellent tables/frames support
Submitter:
Simon Richter
Date:
2005-07-18 03:31:12 UTC
Severity:
wishlist
#168840#5
Date:
2002-11-12 14:18:24 UTC
From:
To:
Hi,

whenever I try to connect to an SSL site, I get the following errors:

SSL error: error:140AD009:SSL routines:SSL_CTX_use_certificate_file:missing asn1 eos

This may or may not be followed by the question whether I want to
connect regardless of a missing peer certificate. If I'm asked and reply
with "y", then I get an empty page, otherwise the page fails to load
entirely.

This happens with all SSL sites, and with the i386 and i486 versions of
libssl.

   Simon

#168840#10
Date:
2002-11-13 03:06:21 UTC
From:
To:
At Tue, 12 Nov 2002 15:18:24 +0100,
Simon Richter wrote:

Which site are you trying to connect to?
Do you have SSL certificate installed and w3m configured to use the
certificate files properly?

Anyway, I think this is a bug of libssl, not w3m.

Regards,
Fumitoshi UKAI

#168840#15
Date:
2002-11-13 07:01:25 UTC
From:
To:
Hi,

The last I tried was savannah.gnu.org.

I have the ca-certificates package installed and w3m set to look for CA
certificates in /etc/ssl/certs. I don't use a client certificate, as I
don't need it.

Hrm, I'm not so sure. I've found out that if you try repeatedly, w3m
hangs, and when sent SIGINT, crashes with a SIGSEGV, where the stack
trace looks like this:

#0  0x0000aae9 in ?? ()
#1  0x08056e56 in strcpy()
#2  0x400cab0a in Gpm_Wgetch() from /usr/lib/libgpm.so.1
#3  0x0807fec9 in wgetch()
#4  0x0804d2bf in strcpy()
#5  0x0804b4b4 in strcpy()
#6  0x402079d3 in __libc_start_main() from /lib/libc.so.6

The trace looks somewhat bogus to me (a lot of symbols are missing, so
these are actually the next public entry points), but #0 is quite
interesting (eax == eip at the point of the crash). The next frame above
contains a "call *%eax", where eax is taken from some structure the
function found a pointer to on the stack. The call is just between two
invokations of signal, where the SIGINT handler is changed just for this
call. I believe that shulg be enough to find the spot where the error is
happening, if not I can compile a debug version.

   Simon

#168840#22
Date:
2002-11-14 21:36:49 UTC
From:
To:
Hi,

Via the 'o' key. Is there another way, besides editing the config file?

   Simon