[squid-users] HTTPS support
acctforjunk at yahoo.com
Wed May 3 18:26:36 UTC 2017
>So, redirect *external* connections to port 3128 to localhost 22, and then SSH
>to your home server on port 3128?
I think what you're saying is it's a port number issue, that certain ports are problematic. But that doesn't seem to be the case. I already run SSH on a non-standard port, and have tried moving SSH to squid's port after moving moving squid elsewhere; it still doesn't work. In addition, I'm able to connect to an entirely different service I run on the same server. So it seems SSH is being filtered
>Squid is an HTTP (and partly FTP) proxy, not a general-purpose TCP proxy.
This is the first I've been told this. I personally don't know since I'm very proxy-illiterate.
From: Antony Stone <Antony.Stone at squid.open.source.it>
To: squid-users at lists.squid-cache.org
Sent: Wednesday, May 3, 2017 12:48 PM
Subject: Re: [squid-users] HTTPS support
On Wednesday 03 May 2017 at 18:37:36, j m wrote:
> I cannot SSH into my home server from an organization that is apparently
> blocking SSH connections, for whatever reason, intentional or not. I am,
> however, able to use a squid proxy that I run from my home server.
So, redirect *external* connections to port 3128 to localhost 22, and then SSH
to your home server on port 3128?
> So the plan was to use SSH through the proxy.
Squid is an HTTP (and partly FTP) proxy, not a general-purpose TCP proxy.
"In fact I wanted to be John Cleese and it took me some time to realise that
the job was already taken."
- Douglas Adams
Please reply to the list;
please *don't* CC me.
squid-users mailing list
squid-users at lists.squid-cache.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the squid-users