piercing corporate FW outbound
Michael ODonnell
michael.odonnell at comcast.net
Fri Feb 6 13:56:48 EST 2004
> A simplistic move could be to try using tcp port 443.
Already tried it.
> As a worst case, you could consider changing to ssh-over-icmp, and
> all of you packets suddenly start looking like pings. There are
> other wrappers that might work too.
They've been blocking ICMP forever.
> All of these said, are you breaking corporate policy by doing this?
If changes in "policy" (and, boy! do I have a "policy"
rant that I'm this close to spewing - don't go there...)
allow parties to an agreement to abrogate the terms
at will, then look out! I can feel some big-time "policy"
changes comin' on!
More information about the gnhlug-discuss
mailing list