Quote:
Originally Posted by blue dragon
^^ That can be blocked on the firewall. Not only can you block tcp/22, you can block the protocol going out on any other port. Remember there is a protocol identifier field in the tcp header, that a firewall can see
|
I see where youre getting at. In my situation, traffic on 22 was blocked. However, I had all ssh traffic being handled on 443 (HTTPS).
Depending on the appliance you use, I can see how they can block the fingerprint of SSH traffic. I just dont know if Blue Coat alone can do this.
Quote:
Originally Posted by E92_SID
Another way you might be able to get around the security if you really wanted to is to connect remotely to your home pc via a service like Go To My PC and then browse what ever sites you want on your home PC through the remote connection.
I am an IT Security Engineer too and plenty of my colleagues do this.
|
On any enterprise that "knows" what they are doing, they would be blocking connections similar to "Go To My PC" or even standard RDP/VNC
If an enterprise allows such connections, its obviously not very secure.