![]() So what makes things confusing is that the same Cisco An圜onnect product can fit any of these descriptions: its protocol is based on DTLS it provides a Java-applet client and it provides a webapp gateway in addition to traditional VPN.īut that doesn't mean the same mode fits all three descriptions at once: e.g. These don't require a dedicated client because they don't actually intercept IP packets from the OS – they work like ordinary websites that you visit over HTTPS (therefore SSL). I don't get why people call this kind "SSL VPNs" (is it because the client runs from a HTTPS website?), but they do it anyway.įinally, "VPNs" which aren't actually IP-layer VPNs but merely web-based gateways (proxies portals) to internal webapps. ![]() Now that's still technically a client, just one that doesn't have to be explicitly installed. VPNs which, regardless of protocol being used, launch a JavaWS or ClickOnce applet directly from a website. (Examples: An圜onnect, SSTP, arguably even OpenVPN.) These still require a client just like any other protocol does – there's nothing magic about the usage of SSL/TLS here, and no great advantage (except perhaps passing through IDS systems unnoticed). VPNs which use TLS or DTLS as their base protocol. I think the common descriptions of "SSL VPNs" conflate three different things: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |