This forum is a read-only archive of the Gammon Software forum (2000–2026). No new posts can be made. Search the archive.

problem occured when connect to a ssl mud

Posted by Jcl on Wed 20 Jul 2005 08:09 AM — 2 posts, 13,817 views.

Jcl #0
I have read the topic
http://www.gammon.com.au/mushclient/stunnel.htm
But It couldn't work. The error is "SSL routines:SSL3_GET_RECORD:wrong version number". Who can help me?



stunnel: stunnel-4.11.exe
openssl: openssl-0.9.7f


stunnel.conf:

client = yes
debug = debug
output = logfile.txt

[furry]
accept = 4567
connect = muck.furry.com:8888


logfile.txt:
2005.07.20 16:02:09 LOG5[2864:2636]: stunnel 4.11 on x86-pc-mingw32-gnu WIN32+IPv6 with OpenSSL 0.9.7f 22 Mar 2005
2005.07.20 16:02:09 LOG7[2864:2924]: RAND_status claims sufficient entropy for the PRNG
2005.07.20 16:02:09 LOG6[2864:2924]: PRNG seeded successfully
2005.07.20 16:02:09 LOG5[2864:2924]: No limit detected for the number of clients
2005.07.20 16:02:09 LOG7[2864:2924]: FD 320 in non-blocking mode
2005.07.20 16:02:09 LOG7[2864:2924]: SO_REUSEADDR option set on accept socket
2005.07.20 16:02:09 LOG7[2864:2924]: furry bound to 0.0.0.0:4567
2005.07.20 16:02:26 LOG7[2864:2924]: furry accepted FD=388 from 127.0.0.1:2333
2005.07.20 16:02:26 LOG7[2864:2924]: Creating a new thread
2005.07.20 16:02:26 LOG7[2864:2924]: New thread created
2005.07.20 16:02:26 LOG7[2864:2276]: furry started
2005.07.20 16:02:26 LOG7[2864:2276]: FD 388 in non-blocking mode
2005.07.20 16:02:26 LOG5[2864:2276]: furry connected from 127.0.0.1:2333
2005.07.20 16:02:26 LOG7[2864:2276]: FD 340 in non-blocking mode
2005.07.20 16:02:26 LOG7[2864:2276]: furry connecting 209.237.26.177:8888
2005.07.20 16:02:26 LOG7[2864:2276]: connect_wait: waiting 10 seconds
2005.07.20 16:02:26 LOG7[2864:2276]: connect_wait: connected
2005.07.20 16:02:26 LOG7[2864:2276]: Remote FD=340 initialized
2005.07.20 16:02:26 LOG3[2864:2276]: SSL_connect: 1408F10B: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number
2005.07.20 16:02:26 LOG7[2864:2276]: furry finished (0 left)
David Haley USA #1
Your problem is quite simply that the receiving end is not a secure connection. You cannot connect with SSL to a server that is not expecting SSL connections.

EDIT:
Disclaimer: Unless, of course, the server is exceedingly clever and takes all connections on one port, figuring out as it receives them whether or not they're for normal telnet or SSL... but this is quite unlikely.