[Lynx-dev] Problems Getting Through to lynx-dev... (fwd)

[Thomas Dickey]

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

---------- Forwarded message ----------
Date: Mon, 26 Sep 2005 09:17:03 -0600
From: John Red-Horse <address@hidden>
To: address@hidden
Subject: Problems Getting Through to lynx-dev...

Hey Thomas,

I really hate to bother you, but I tried to send the attached message to
the lynx-dev mailing list for some help on a problem I'm having between
two versions of lynx I use on two different systems my ISP uses.

Can you forward this to the list for me?

many, many thanks,
john red-horse
tijeras, nm
> --- Begin Message ---
>
>
>
> Subject: 
>
> Problems With A User/Password Login Submit
>
>
>
>
> Date: 
>
> Fri, 23 Sep 2005 15:00:16 -0600
>
>
>
>
> User-agent: 
>
> Mutt/1.5.9i
>
>
>
>
> Dear Pros,
>
> On one of the systems that I use on my ISP's network, I'm having a
> problem logging into my account at wsj.com via the https-savvy form.
>
> Let me provide some background.
>
> One is running a Linux OS (this is the system that fails to make the
> connection properly):
>
>  Linux chishio 2.4.29-rc1 #1 SMP Fri Jan 7 16:41:59 MST 2005 i686 GNU/Linux
>
> with lynx version (as reported from https://www.gnutls.org:5555/):
>
>  Client's browser version: Lynx/2.8.5rel.1 libwww-FM/2.14 SSL-MM/1.4.1
>  GNUTLS/1.0.16
>
>  Cipher key size: 128
>
> the other is SunOS:
>
>  SunOS yagi 5.8 Generic_108528-10 sun4u sparc SUNW,UltraSPARC-IIi-Engine
>
>  Client's browser version: Lynx/2.8.4rel.1 libwww-FM/2.14 SSL-MM/1.4.1
>  OpenSSL/0.9.4
>
>  Cipher key size: 192
>
> The WSJ login script appears to be expecting a TLS encryption key (as
> best as I can figure from the trace file) of a specific size.
>
> This is a portion of the trace for the failed, linux version of lynx:
>
> ----------------------begin trace snippet----------------------
>                 Lynx Trace Log (2.8.5rel.1)
>
> User message: Trace ON!
> GETCH: Got 0x103.
> LYReadCmdKey(0) ->Up Arrow (0x100)
> GETCH: Got 0x78.
> LYReadCmdKey(0) ->x (0x78)
> SubmitForm
>   link_name=
>   link_value=Log In
>
> [snip]
>
> Looking up users2.wsj.com
> Making HTTPS connection to users2.wsj.com
> TCP: Error 115 in `SOCKET_ERRNO' after call to this socket's first connect()
> +failed.
>         Operation now in progress
> TCP: Error 115 in `SOCKET_ERRNO' after call to this socket's first select()
> +failed.
>         Operation now in progress
> Retrying connection without TLS.
> HTParse: aName:`https://users2.wsj.com/lmda/do/submitLogin'
>    relatedName:`'
>    want: host
> HTParse:      result:`users2.wsj.com'
> Looking up users2.wsj.com
> Making HTTPS connection to users2.wsj.com
> TCP: Error 115 in `SOCKET_ERRNO' after call to this socket's first connect()
> +failed.
>         Operation now in progress
> TCP: Error 115 in `SOCKET_ERRNO' after call to this socket's first select()
> +failed.
>         Operation now in progress
> HTTP: Unable to complete SSL handshake for
> +'https://users2.wsj.com/lmda/do/submitLogin', SSL_connect=0, SSL error stack
> +dump follows
> HTTP: SSL: A TLS packet with unexpected length was received.
> ----------------------end trace snippet----------------------
>
> and this is a portion of the trace from the SunOS edition that does
> connect correctly:
>
> ----------------------begin trace snippet----------------------
>
>                 Lynx Trace Log (2.8.4rel.1)
>
> User message: Trace ON!
> GETCH: Got 0xa.
> LYReadCmdKey(0) ->
>  (0xa)
> SubmitForm
>   link_name=
>   link_value=Log In
>
> [snip]
>
> Looking up users2.wsj.com
> HTParseInet: parsing `users2.wsj.com'.
> LYGetHostByName: parsing `users2.wsj.com'.
> End of LYGetHostByName: 2dc4c4 { h_name = 2dc4d8 "users2.wsj.com",
>          h_aliases = 2dc4f0 { 0x0 },
>          h_addrtype = 2, h_length = 4,
>          h_addr_list = 2dc4e8 { 2dcdf4 "206.157.193.72", 0x0 } }
> LYGetHostByName: Resolved name to a hostent.
> HTParseInet: Parsed address as port 443, IP address 206.157.193.72
> Making HTTPS connection to users2.wsj.com
> TCP: Error 150 in `SOCKET_ERRNO' after call to this socket's first connect()
> +failed.
>         Operation now in progress
> TCP: Error 150 in `SOCKET_ERRNO' after call to this socket's first select()
> +failed.
>         Operation now in progress
> Secure 128-bit TLSv1/SSLv3 (RC4-SHA) HTTP connection
>
> ----------------------end trace snippet----------------------
>
> It'd really be nice if someone could show me what the issue is so that I
> could go to the sysadmins and tell them the fix...
>
> many thanks,
> john
>
>
> --- End Message ---