Try this..
./openssl s_client -tls1 -connect www.cia.gov:443
On 10/24/07, Lutz Jaenicke <[EMAIL PROTECTED]> wrote:
>
> Isolating the problem is more or less simple:
> openssl s_client -connect www.cia.gov:443
> shows the intermittent failures as well, so we can rule out all
> applications (cur
On Tue, 2007-10-23 at 22:02 -0700, Alex Lam wrote:
> That's TLSv1, not SSLv2.
>
> : 01 03 01 00 63 00 00 00 10 00 00 39 00 00 38 00 c..9..8.
> 0010: 00 35 00 00 88 00 00 87 00 00 84 00 00 16 00
> 00 .5..
> 0020: 13 00 00 0a 07 00 c0 00 00 33 00 00 32 00 00 2f .3..2
Isolating the problem is more or less simple:
openssl s_client -connect www.cia.gov:443
shows the intermittent failures as well, so we can rule out all
applications (curl, wget, ...). Has to be some basic thing.
I tend to observe the failure with s_client not on the first attempt but
on the nth
That's TLSv1, not SSLv2.
: 01 03 01 00 63 00 00 00 10 00 00 39 00 00 38 00 c..9..8.
0010: 00 35 00 00 88 00 00 87 00 00 84 00 00 16 00 00 .5..
0020: 13 00 00 0a 07 00 c0 00 00 33 00 00 32 00 00 2f .3..2../
0030: 00 00 45 00 00 44 00 00 41 00 00 07 05 00 80 03 ..E..D
Marek Marcola wrote:
> I think that this is CIA webserver problem.
> You may test this with:
> $ openssl s_client -connect www.cia.gov:443 -state -debug -msg [[-ssl3]
> [-tls1]]
> and in any combination after some successful connection you will get failed
> connections.
> For example:
> $ opens
Hello,
> We use curl to retrieve webpages, and recently started receiving an
> intermittent (40-60% of the time) error when retrieving a page from the
> CIA. About two weeks ago, they switched to running https only, with the
> http URLs being forwarded to the https equivalents.
>
> The error we re
Hey all:
We use curl to retrieve webpages, and recently started receiving an
intermittent (40-60% of the time) error when retrieving a page from the
CIA. About two weeks ago, they switched to running https only, with the
http URLs being forwarded to the https equivalents.
The error we receive is:
