Which version (number, distribution) of OpenSSL are you using? The line
number s23_clnt.c:607 might tell us something.
Could you get a packet capture (Wireshark, tshark, tcpdump, etc.)?
It's probably only a few KB of the packets which are relevant to the
failed connection attempt.
On 05/27/2011
On 05/27/2011 11:53 AM, alex wrote:
On 05-27 11:39, Marsh Ray wrote:
Which version (number, distribution) of OpenSSL are you using?
0.9.8o-5ubuntu1
Could you get a packet capture (Wireshark, tshark, tcpdump, etc.)?
I'll try. But I'm running a Tor Relay, so isolating my traffic is kind
of h
On 05-27 11:39, Marsh Ray wrote:
Which version (number, distribution) of OpenSSL are you using?
0.9.8o-5ubuntu1
Could you get a packet capture (Wireshark, tshark, tcpdump, etc.)?
I'll try. But I'm running a Tor Relay, so isolating my traffic is kind
of hard :)
True, but I actually want t
Hi,
alex wrote (27 May 2011 15:35:55 GMT) :
> Torifying it causes the TLS handshake to fail:
> % torify openssl s_client -connect 83.223.73.105:465
> CONNECTED(0003)
> 24520:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown
> protocol:s23_clnt.c:607:
> Any idea?
Not really, but ena
On 05-27 17:56, intrigeri wrote:
Not really, but enabling starttls mode makes it work:
$ /usr/bin/torify openssl s_client -starttls smtp -connect 83.223.73.105:465
True, but I actually want to *not* do that.
--
alex
-- It's funny how the colors of the real world only
seem really real when
I have been getting a weird error with an STMP-TLS connection over Tor
(0.2.1.30)
This direct connection works:
% openssl s_client -connect 83.223.73.105:465
CONNECTED(0003)
depth=2 /O=Root CA/OU=http://www.cacert.org/CN=CA Cert Signing
Authority/emailAddress=supp...@cacert.org
verify er
