Well whilst on a different search; actually cryptology I came upon this:

http://www.freedom.net/products/websecure/index.html

Reads quite well and comes sort of recommended. I'm not sure if it would sneak past or even if you should use it...I'm just saying I might use it at some point since we have websense poorly implemented here I just turn the browser proxy settings off and go via manually entered dns/gateway At least I hope I do....eek

Have used it in the past for reasons i will not divulge here

It worked for what i needed it for at the time....

Oh and if your after a good book for Christmas this is a great read:

http://www.cryptonomicon.com/

And this is quite an ammusing essay

http://www.cryptonomicon.com/beginning.html

Could be time for testing of this over crimble in work.

Websense?

SSH Client [local tunnels] -> NTLM Proxy [google?] -> [restricted]Http Proxy -> THE NET -> Home [ADSL?] Router:443->22 -> SSH:22 [Linux etc] -> Home Proxy Server [squid on Linux]

Free

Point your browser at the SSH Client (with local port 'tunnels' which map to ports on the remote SSH machine), NTLM adds (wraps) your domain details for the Websense/M$ Proxy, The router is connected to on 443, emulating a https [sSL] website (proxy won't complain about ports 80 and 443;)), and you can either run the SSH server on 443 or have the router 'NAT' the 443 request down to port 22 (SSH server).

I can vouch this works fine

Rich

Remote desktop client on port 80 > NET > Home router, nat 80 to proper RDP port > Desktop.