http://10.10.14.2:443 conect
https://10.10.14.2:443 erro
Help
OpenSSLComando
2006.08.22 02:15:00 LOG5[464:3504]: stunnel 4.15 on x86-pc-mingw32-gnu with OpenSSL 0.9.7i 14 Oct 2005
2006.08.22 02:15:00 LOG5[464:3504]: Threading:WIN32 SSL:ENGINE Sockets:SELECT,IPv6
2006.08.22 02:15:00 LOG5[464:3492]: No limit detected for the number of clients
2006.08.22 02:21:20 LOG5[464:2988]: https connected from 10.10.14.1:54032
2006.08.22 02:21:20 LOG5[464:3264]: https connected from 10.10.14.1:34300
2006.08.22 02:21:20 LOG3[464:2988]: SSL_connect: Peer suddenly disconnected
2006.08.22 02:21:20 LOG5[464:2988]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket
2006.08.22 02:21:20 LOG3[464:3264]: SSL_connect: Peer suddenly disconnected
2006.08.22 02:21:20 LOG5[464:3264]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket
2006.08.22 02:21:20 LOG5[464:2984]: https connected from 10.10.14.1:55070
2006.08.22 02:21:20 LOG3[464:2984]: SSL_connect: Peer suddenly disconnected
2006.08.22 02:21:20 LOG5[464:2984]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket
2006.08.22 02:21:20 LOG5[464:1992]: https connected from 10.10.14.1:55480
2006.08.22 02:21:20 LOG3[464:1992]: SSL_connect: Peer suddenly disconnected
2006.08.22 02:21:20 LOG5[464:1992]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket
2006.08.22 02:21:20 LOG5[464:3200]: https connected from 10.10.14.1:41328
2006.08.22 02:21:20 LOG3[464:3200]: SSL_connect: Peer suddenly disconnected
2006.08.22 02:21:20 LOG5[464:3200]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket
2006.08.22 02:21:20 LOG5[464:3408]: https connected from 10.10.14.1:60292
2006.08.22 02:21:20 LOG3[464:3408]: SSL_connect: Peer suddenly disconnected
2006.08.22 02:21:20 LOG5[464:3408]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket
2006.08.22 02:21:22 LOG5[464:2088]: https connected from 10.10.14.1:42477
2006.08.22 02:21:22 LOG3[464:2088]: SSL_connect: Peer suddenly disconnected
2006.08.22 02:21:22 LOG5[464:2088]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket
2006.08.22 02:21:22 LOG5[464:3036]: https connected from 10.10.14.1:55688
2006.08.22 02:21:22 LOG3[464:3036]: SSL_connect: Peer suddenly disconnected
2006.08.22 02:21:22 LOG5[464:3036]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket
2006.08.22 02:21:22 LOG5[464:3320]: https connected from 10.10.14.1:39588
2006.08.22 02:21:22 LOG3[464:3320]: SSL_connect: Peer suddenly disconnected
2006.08.22 02:21:22 LOG5[464:3320]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket
2006.08.22 02:21:26 LOG5[464:2060]: https connected from 10.10.14.1:56992
2006.08.22 02:21:26 LOG3[464:2060]: SSL_connect: Peer suddenly disconnected
2006.08.22 02:21:26 LOG5[464:2060]: Connection reset: 0 bytes sent to
--
======
SSL, 0 bytes sent to socket; Sample stunnel configuration file by Michal Trojnara 2002-2006
; Some options used here may not be adequate for your particular configuration
; Certificate/key is needed in server mode and optional in client mode
; The default certificate is provided only for testing and should not
; be used in a production environment
cert = stunnel.pem
key = stunnel.pem
; Some performance tunings
socket = l:TCP_NODELAY=1
socket = r:TCP_NODELAY=1
; Workaround for Eudora bug
;options = DONT_INSERT_EMPTY_FRAGMENTS
; Authentication stuff
;verify = 2
; Don't forget to c_rehash CApath
;CApath = certs
; It's often easier to use CAfile
;CAfile = certs.pem
; Don't forget to c_rehash CRLpath
;CRLpath = crls
; Alternatively you can use CRLfile
;CRLfile = crls.pem
; Some debugging stuff useful for troubleshooting
;debug = 7
;output = stunnel.log
; Use it for client mode
client = yes
; Service-level configuration
[pop3s]
accept = 995
connect = 110
[imaps]
accept = 993
connect = 143
[ssmtp]
accept = 465
connect = 25
[https]
accept = 10.10.14.2:443
connect = 10.10.14.2:80
TIMEOUTclose = 0
; vim:ft=dosini