Based on your question, I take it you are talking about the new technology whereby you can access your internal network from the Internet using an SSL connection to a server, that then connects to your internal network.
That technology is very limited, and is not intended to provide a "total" network connection, providing you all the same access as if you were physically located at your company. The plans for SSL VPN is to basically provide file/print operations. You won't have Client/Server access to Exchange, or SQL, or connectivity such as that.
The simple way to explain would be the layer differences. ipsec based vpn works on network layer (effectively works no matter what application produces the traffic). But for SSL (application layer) all the applications need to support that. The only other way would be to use a proxy solution where you can have a ssl connection to a server and access other resources. But that is not popular yet.
40-bit SSL (Secure Server) IDs, are ideal for security-sensitive intranets, extranets, and Web sites. They enable 40-bit SSL when communicating with export-version Netscape and Microsoft Internet Explorer browsers (used by most people in the U.S. and worldwide), and 128-bit SSL encryption when communicating with domestic-version Microsoft and Netscape browsers. 40-bit SSL (Secure Server) IDs run on virtually all server software platforms.
128-bit SSL Encryption
128-bit SSL IDs, enable the world's strongest SSL encryption with both domestic and export versions of Microsoft® and Netscape® browsers. 128-bit SSL is the standard for large-scale online merchants, banks, brokerages, health care organizations, and insurance companies worldwide. 128-bit IDs can run on server software from any non-U.S. software vendor, or software from a U.S. software vendor properly classified by the U.S. Department of Commerce.
The primary difference between the two types of Server IDs is the strength of the SSL session that each enable. Secure Sockets Layer (SSL) technology is the industry-standard method for protecting Web communications developed by Netscape Communications Corporation. The SSL security protocol provides data encryption, server authentication, message integrity, and optional client authentication for a TCP/IP connection. Because SSL is built into all major browsers and Web servers, simply installing a digital certificate turns on their SSL capabilities.
SSL comes in two strengths, 40-bit and 128-bit, which refer to the length of the 'session key' generated by every encrypted transaction. The longer the key, the more difficult it is to break the encryption code. Most browsers support 40-bit SSL sessions, and the latest browsers enable users to encrypt transactions in 128-bit sessions - trillions of times stronger than 40-bit sessions.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR
and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity
options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in
HA DocumentationCode download linksGoalRequirementLimitationsSupported
ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationCo...
Question I am currently unable to specify "crypto keyring" command when
configuring VPN connection on my cisco 2901 router. The following
licenses have been activated on my router :