C O N T E N T S |
|||||||||
| Secure Web Server Documentation
| Chapter 2:
| Introduction to SSL__Topics_____________________________________ What is SSL?Secure Sockets Layer (SSL) is the open standard security protocol for the secure transfer of sensitive information over the Internet. Implementing SSL requires software to be installed in servers and on browsers that use the SSL protocol. SSL provides three things: privacy through encryption, server authentication, and message integrity. Client authentication is available as an optional function. With your SSL_aware Secure Web Server you can ensure a level of security that cannot be achieved by other means. SSL is the most widely used secure method for transmitting sensitive information across the Internet, extranets, and intranets.
Important: SSL data transport requires encryption. Many governments, including the United States, have restrictions on the import and export of cryptographic algorithms. Please ensure that your use of SSL is in compliance with all national and international laws that apply to you. How widely used is SSL?SSL is a cooperative technology, requiring reciprocating server and client technologies. Both Netscape and Microsoft have built full_featured SSL security into their browsers. Security and trust are pivotal to the rapid development of eBusiness. More and more web sites are using the SSL protocol to offer clients secure connections and to exchange confidential information. In addition to server_side security, client authentication, also using the SSL protocol for digital IDs and signatures, is gaining much wider acceptance. By convention, Web pages that require an SSL connection start with https : instead of http: (in the browser's address field). Whenever you enter a secure connection, your browser also shows the familiar padlock image in the status bar, indicating that the page is encrypted.
Depending on your browser and its security settings, you may be unaware of the authentication process unless you are prompted to install a certificate issued by the server. This is because your browser has a store of certificates signed by the same certifying authorities as most servers use (such as VeriSign, for example). You can easily view your certificate store and the details of individual certificates.
How are Apache_SSL, mod_ssl, and OpenSSL related?Fortunately, open_source implementations of SSL for Apache are available. The original Apache implementation of SSL was Apache_SSL . Subsequently, mod_ssl was derived from Apache_SSL and has become an alternative to it. In open source terminology, mod_ssl is a "split" _ derived from Apache_SSL but extensively redeveloped, so the code now bears little relation to the original. Apache_SSL continues to be developed and maintained, with the focus being on reliability, security and performance within a limited feature set. The increasing popularity of mod_ssl among Apache users is a result of its added_value features and quality. The mod_ssl package is not standalone: it works in conjunction with OpenSSL. OpenSSL
represents a collaborative effort to develop a robust, commercial_grade, full_featured, and open_source toolkit. It implements the
SSL Versions 2 and 3 and
Transport Layer Security (TLS)
Version 1
protocols, as well as a full_strength, general_purpose cryptography library.
You can think of mod_ssl as the glue joining OpenSSL with
Secure Web Server
. The mod_ssl interface provides Apache 1.3.12 web server (on which
CSWS
is based) with full use of the OpenSSL toolkit. CSWS
uses RSA Security's Crypto_C (BSAFE
) library in OpenSSL.
| |||||||
| The mod_ssl package integrates the OpenSSL module with a set of source patches for Apache called the Extended API (EAPI) . These components are included and automatically installed in Secure Web Server : the OpenVMS implementation of Apache with SSL. |