| 1 |
On 22 February 2012 12:07, Helmut Jarausch <jarausch@××××××××××××××××.de> wrote: |
| 2 |
> On 02/19/2012 07:15:46 PM, Mick wrote: |
| 3 |
>> Hi All, |
| 4 |
>> |
| 5 |
>> I am trying to set up a reverse-proxy at my home to be able to by- |
| 6 |
>> pass |
| 7 |
>> |
| 8 |
>> restrictive firewalls that only allow http/https traffic. |
| 9 |
>> |
| 10 |
> |
| 11 |
> If you only want to get through your firewall by using the open port |
| 12 |
> 80, I'd use ssh's port forwarding capablities. |
| 13 |
> |
| 14 |
> You might have a look at |
| 15 |
> |
| 16 |
> https://help.ubuntu.com/community/SSH/OpenSSH/PortForwarding |
| 17 |
> |
| 18 |
> You can use 'localhost' as "man in the middle". |
| 19 |
|
| 20 |
Thanks Helmut. |
| 21 |
|
| 22 |
This will only work if I set sshd at my home server to listen for |
| 23 |
connections on port 443 or 80 (all other ports are blocked by the |
| 24 |
gateway behind which I happen to be) and the gateway does not perform |
| 25 |
deep packet inspection. |
| 26 |
|
| 27 |
Hence, tunneling ssh via https is the only sure-fire way of getting |
| 28 |
through restrictive firewalls and corporate internet gateways. |
| 29 |
|
| 30 |
-- |
| 31 |
Regards, |
| 32 |
Mick |
Archives