On Sat, 1 Mar 2008 14:59:51 +0000 Brett Parker iDunno@sommitrealweird.co.uk allegedly wrote:
*YAWN* - most don't block port 443, I have a ssh daemon listening on port 443 of one of my VMs, otherwise there's lots of other ways of "getting round" stupid access limits on broken notworks.
See earlier response. In my experience I've been intercepted by a transparent proxy asking for authentication (and usually a credit card). The network then limits you to 80/443 and sometimes 25/110/143
I confess I've never checked whether the intercept on 443 was a packet filter or a protocol block, but again since I only connect to my mail provider's servers and not to a server I control on my home network it becomes irrelevant whether I can punch ssh through on that port. Of course if, like you, I ran an ssh daemon on 443 at home it might be useful - but I don't.
Mick
---------------------------------------------------------------------
This is a Microsoft free zone. Please do not send me Microsoft Word Documents. For some reasons, see:
http://www.gnu.org/philosophy/no-word-attachments.html http://www.goldmark.org/netrants/no-word/attach.html ---------------------------------------------------------------------