[sslh] Fw: Assistance needed please! Proxytunnel --> stunnel --> sslh --> ssh server (Windows 10)
mkanet at yahoo.com
mkanet at yahoo.com
Tue Dec 24 21:14:22 UTC 2019
I just realized something... in this entire setup, I haven't specified my SSH username/password anywhere. I just realized I'm missing a very important step. Could someone please be kind enough to tell me how to use putty so that it uses Proxytunnel's port 7000 (specified via the -a parameter)? All the docs I've seen seem to be meant for executing Proxytunnel executable… instead of using Proxytunnel's -a parameter and respective listening port. I would rather access it via it's listening port.
Merry Christmas!!
===========
I used to have proxytunnel --> stunnel --> sslh -->ssh server working perfectly on my Win10 machines. However, it stopped working a little while back. I haven't changed any of my configuration; at least, not deliberately. I’ve spent a lot of time trying to get it working again with no luck. I'm REALLY hoping someone can tell me what I'm doing wrong.
Sockets appear to connect and close as they should with no errors (see below respective logs). However, my web browser doesn’t receive the data from my SSH server.
Laptop (proxytunnel):
proxytunnel.exe -a 7000 -e -p PUBLICPROXYIP:808 -d MYURL.COM:443
Web browser (Chrome) pointed to: socks proxy = 127.0.0.1:7000
MyServer (stunnel)
stunnel.confoutput = stunnel.log
sessionCacheSize = 0
fips = no
cert = stunnel.pem
options = NO_SSLv2
client= No
socket = l:TCP_NODELAY=1
socket = r:TCP_NODELAY=1[stunnel-sslh]
accept = 192.168.1.2:443
connect = 192.168.1.2:7777
Debug log file:
2019.12.24 00:49:28 LOG5[6040]: Service [stunnel-sslh] accepted connection from 192.168.1.2:53515
2019.12.24 00:49:28 LOG5[6040]: s_connect: connected 192.168.1.2:7777
2019.12.24 00:49:28 LOG5[6040]: Service [stunnel-sslh] connected remote server from 192.168.1.2:53516
2019.12.24 00:49:28 LOG5[6040]: Connection closed: 100 byte(s) sent to SSL, 14 byte(s) sent to socket
2019.12.24 00:49:31 LOG5[13840]: Service [stunnel-sslh] accepted connection from 192.168.1.2:53518
2019.12.24 00:49:31 LOG5[13840]: s_connect: connected 192.168.1.2:7777
2019.12.24 00:49:31 LOG5[13840]: Service [stunnel-sslh] connected remote server from 192.168.1.2:53519
2019.12.24 00:49:31 LOG5[13840]: Connection closed: 100 byte(s) sent to SSL, 14 byte(s) sent to socket
MyServer (sslh)
sslh-select.exe -f -p 192.168.1.2:7777 --ssh 192.168.1.2:8888 --http 192.168.1.2:80
Debug log output:
sslh-select 1.14 started2019-12-24 02:39:19 MyPC.MYURL.COM:58566 MyPC.MYURL.COM:8888
2019-12-24 02:39:20 MyPC.MYURL.COM:58567 MyPC.MYURL.COM:8888
2019-12-24 02:39:20 MyPC.MYURL.COM:58568 MyPC.MYURL.COM:8888
2019-12-24 02:39:20 MyPC.MYURL.COM:58579 MyPC.MYURL.COM:8888
2019-12-24 02:39:20 MyPC.MYURL.COM:58580 MyPC.MYURL.COM:8888
2019-12-24 02:39:20 MyPC.MYURL.COM:58581 MyPC.MYURL.COM:8888
2019-12-24 02:39:20 MyPC.MYURL.COM:58582 MyPC.MYURL.COM:8888
2019-12-24 02:39:21 MyPC.MYURL.COM:58583 MyPC.MYURL.COM:8888
2019-12-24 02:39:21 MyPC.MYURL.COM:58584 MyPC.MYURL.COM:8888
2019-12-24 02:39:21 MyPC.MYURL.COM:58585 MyPC.MYURL.COM:8888
2019-12-24 02:39:22 MyPC.MYURL.COM:58586 MyPC.MYURL.COM:8888
2019-12-24 02:39:22 MyPC.MYURL.COM:58587 MyPC.MYURL.COM:8888
2019-12-24 02:39:22 MyPC.MYURL.COM:58588 MyPC.MYURL.COM:8888
2019-12-24 02:39:22 MyPC.MYURL.COM:58597 MyPC.MYURL.COM:8888
2019-12-24 02:39:22 MyPC.MYURL.COM:58637 MyPC.MYURL.COM:8888
MyServer (Bitvise SSH Server)
Listening interface: 0.0.0.0
Listening port: 8888
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rutschle.net/pipermail/sslh/attachments/20191224/7aca9670/attachment.html>
More information about the sslh
mailing list