« Aircraft Security Seals | Main | Limiting the President's ability to conduct war... »
October 5, 2005
Defining connectivity up
I remember when your average standards meeting didn't have any Internet connectivity at all. This week I'm at the IEEE 1609.1 meeting in Albany, NY. They have wireless but are people happy? No.... They're too busy complaining that a bunch of ports (Jabber/SSL [5223], POP3S [1995], ...) are blocked.Posted by ekr at October 5, 2005 1:52 PM | Filed under:
Comments
Isn't this the reason why you leave an SSH server running on port 443 somewhere? Port forwarding is your friend...
Though personally I would sometimes welcome an excuse to not be checking email.
Posted by: Jack Lloyd at October 5, 2005 6:21 PM
Actually, SSH is unblocked, so I'm quite able to get out. Some of the other attendees don't seem to have it.
Posted by: EKR at October 5, 2005 7:27 PM
In principle running an sshd on port 443 isn't enough, since it's easy to distinguish ssh from ssl at the firewall or HTTP proxy. Of course, if you find yourself in an environment where TPTB are doing that, that's probably a clue that they don't want you to be sshing anyway.
Posted by: Chris Lightfoot at October 6, 2005 6:07 AM