Secure Sockets Layer: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Sandy Harris
No edit summary
mNo edit summary
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
{{subpages}}
{{PropDel}}<br><br>{{subpages}}
'''Secure Sockets Layer (SSL)''' is an  [[cryptography#two-way encryption|encrypted]] end-to-end [[protocol (computer)| protocol]] that runs between [[World Wide Web]] browsers (i.e., [[Hypertext Transfer Protocol]] *HTTP) clients) and Web servers. It was developed by Netscape
'''Secure Sockets Layer (SSL)''' is an  [[cryptography#two-way encryption|encrypted]] end-to-end [[protocol (computer)| protocol]] that runs between [[World Wide Web]] browsers (i.e., [[Hypertext Transfer Protocol]] *HTTP) clients) and Web servers. It was developed by Netscape
<ref name="schneierbook">{{citation  
<ref name="schneierbook">{{citation  
Line 19: Line 19:


==References==
==References==
{{reflist|2}}
{{reflist|2}}[[Category:Suggestion Bot Tag]]

Latest revision as of 16:00, 16 October 2024

This article may be deleted soon.
To oppose or discuss a nomination, please go to CZ:Proposed for deletion and follow the instructions.

For the monthly nomination lists, see
Category:Articles for deletion.


Secure Sockets Layer (SSL) is an encrypted end-to-end protocol that runs between World Wide Web browsers (i.e., Hypertext Transfer Protocol *HTTP) clients) and Web servers. It was developed by Netscape [1], and supported by Microsoft and other major vendors until the development of a functionally equivalent standard, Transport Layer Security (TLS) [2], by the Internet Engineering Task Force. TLS is a derivative of SSL.

From the standpoint of network architecture, it forms a "shim" between Transmission Control Protocol (TCP) and HTTP. "Sockets" refer to the programming interface used by the host and client application to communicate only when traffic has been encrypted before being sent to TCP, or decrypted after it is received. For cryptographic authentication and content protection, SSL uses public key software from RSA.

There is no charge for client-side access or noncommercial server use; Netscape does license the server side for commercial service.

References

  1. Schneier, Bruce (2nd edition, 1996,), Applied Cryptography, John Wiley & Sons, ISBN 0-471-11709-9
  2. T. Dierks, E. Rescorla (August 2008), The Transport Layer Security (TLS) Protocol Version 1.2., RFC5246