Anyone have a spare port 443 ?

DaveQB · Post by **DaveQB** » Tue Oct 31, 2006 8:58 pm

Here at work they block all ports besides 80 and 443 from our computers.

So the only way I have been able to ssh to my home was to run sshd on 443 at home [and then ssh to other servers from there]

But in the middle of moving house, so havent got that options right now, well not for long anyway.

Anyone not using port 443 that can run an sshd process on that port to allow me to use to then ssh to places I need to get to ?

Cheers for any consideration.

schotty · Post by **schotty** » Thu Nov 02, 2006 8:41 pm

Have you gotten a bite yet?

DaveQB · Post by **DaveQB** » Thu Nov 02, 2006 9:43 pm

Ahh yes thanks schotty

A generous tllts member has helped out.
What a great community we have.

Thanks all the same though.

DaveQB · Post by **DaveQB** » Thu Jun 28, 2007 9:52 pm

FYI

If you sign up for a free shell account at bur.st you can get ssh access to it on ANY port.

Quote: http://www.bur.st/support.html#GettingAround

Some users find themselves on networks that do not allow external SSH access. shell.bur.st is actually entirely dedicated to ssh, which means you can connection on any TCP port (port 1 through to 65535) and get a valid SSH connection. Examples:

* Your network blocks outgoing connections to TCP/22 and all unprivledged ports. Solution: Point your SSH client to shell.br.st:789 (a random privledged port).
* Your network blocks all outgoing access except web browsing. Solution: Point your SSH client to connect to shell.bur.st on port 80 or 443.
* Your network blocks all outgoing connections. You can only use an http web proxy. Solution: use Putty's "connect through web proxy" setting to connect to shell.bur.st port 80 via the web proxy.
* If you are blocked from accessing webmail.bur.st you might try connecting to mebwail.bur.st as an alternative, as many corporate firewalls and proxies ban connections to any hosts with 'webmail' in them.

Top stuff!!
Good work bur.st team!