09.07.2015 Views

Firebox SSL VPN Gateway Administration Guide - WatchGuard ...

Firebox SSL VPN Gateway Administration Guide - WatchGuard ...

Firebox SSL VPN Gateway Administration Guide - WatchGuard ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Firebox</strong> <strong>SSL</strong> Overviewthe correct port numbers so that the packets return to the correctapplication.The <strong>Firebox</strong> <strong>SSL</strong> tunnel is established using industry standardconnection establishment techniques such as HTTPS, ProxyHTTPS, and SOCKS. This operation makes the <strong>Firebox</strong> <strong>SSL</strong> firewallfriendly and thus allows remote computers to access privatenetworks from behind other organization firewalls without creatingany problems.For example, the connection can be made via an intermediateproxy, such as an HTTP proxy, by issuing a CONNECT HTTPScommand to the intermediate proxy. Any credentials requestedby the intermediate proxy, will be in turn obtained from theremote user (by using single signon information or by requestingthe information from the remote user) and presented to theintermediate proxy server. Once the HTTPS session is established,the payload of the session is encrypted and carries securepackets to the <strong>Firebox</strong> <strong>SSL</strong>.Terminating the Secure Tunnel and ReturningPackets to the ClientThe <strong>Firebox</strong> <strong>SSL</strong> terminates the <strong>SSL</strong> tunnel and accepts anyincoming packets destined for the private network. If the packetsmeet the authorization and access control criteria, the <strong>Firebox</strong><strong>SSL</strong> regenerates the packet IP headers so that they appearto originate from the <strong>Firebox</strong> <strong>SSL</strong>’s private network IP addressrange or the client-assigned private IP address. The <strong>Firebox</strong> <strong>SSL</strong>then injects the packets into the network.NOTEIf you run a packet sniffer such as Ethereal on the PC wherethe Secure Access client is running, you will see unencryptedtraffic that appears to be between the client and the <strong>Firebox</strong><strong>SSL</strong>. That unencrypted traffic, however, is not over the tunnelbetween the client and the <strong>Firebox</strong> <strong>SSL</strong> but rather the tunnelto the local applications.The Secure Access client maintains two tunnels: an <strong>SSL</strong>tunnel over which data is sent to the <strong>Firebox</strong> <strong>SSL</strong> (the snifferalso detects this tunnel) and a tunnel between the client andlocal applications. The encrypted data that arrives over the<strong>SSL</strong> tunnel is then decrypted before being sent to the localapplication over the second tunnel. The packet sniffer sees12 <strong>Firebox</strong> <strong>SSL</strong> <strong>VPN</strong> <strong>Gateway</strong> <strong>Administration</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!