-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "Bodo" == Bodo Moeller <[EMAIL PROTECTED]> writes:
Bodo> Holger Reif pointed out that this is a known server bug for
Bodo> which a workaround exists (openssl s_client -bugs enables the
Bodo> whole bunch of them). In this case, the
Bodo> SSL_OP_NETSCAPE_CHALLENGE_BUG option solves the problem. So it
Bodo> may make sense to set various options during the Lynx-SSL
Bodo> reconnection.
(BTW: it was bank.netbank.com rather than banking.wellsfargo.com that
lynx will not connect to. I confused the two when posting.)
The patch (lynx-282-ssl-p2.patch) I have does:
ssl_ctx = SSL_CTX_new(SSLv23_client_method());
SSL_CTX_set_options(ssl_ctx, SSL_OP_ALL);
a la s_client's -bugs argument.
I just did a test. (Should have done so before posting the first note
[SIGH]...) I compiled three shared lib each with a single function
named SSLv23_client_method() which only called FOO_client_method() for
each FOO in SSLv2, SSLv3 and TLSv1 and tried lynx LD_PRELOADing each
in turn. The first two allowed me to connect as I need.
(Unfortunately Net.B@nk's ECMAscript submit button (<INPUT
TYPE="BUTTON" VALUE="Login" OnClick="ProcessForm()">) doesn't show up
as clickable in lynx (even w/ ECMAscript support compiled in)....
- -JimC
- --
James H. Cloos, Jr. <http://www.jhcloos.com/cloos/public_key> 1024D/ED7DAEA6
<[EMAIL PROTECTED]> E9E9 F828 61A4 6EA9 0F2B 63E7 997A 9F17 ED7D AEA6
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.7 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE3bDSSmXqfF+19rqYRAsloAJ9zNgYuRXCHiAVB4ju1eYRxyc7e6ACeMVWl
2+5CPied/LJjk+w9gHHCd5I=
=J5do
-----END PGP SIGNATURE-----
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
