dido:public:ra:xapend:xapend.b_stds:tech:ietf:tls
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:tech:ietf:tls [2021/08/06 13:07] murphy |
dido:public:ra:xapend:xapend.b_stds:tech:ietf:tls [2021/08/17 13:37] (current) murphy |
||
|---|---|---|---|
| Line 26: | Line 26: | ||
| data [[dido:public:ra:xapend:xapend.a_glossary:e:encryption|encryption]] (e.g., DES [[https://tools.ietf.org/html/rfc2246#ref-DES | DES]] | data [[dido:public:ra:xapend:xapend.a_glossary:e:encryption|encryption]] (e.g., DES [[https://tools.ietf.org/html/rfc2246#ref-DES | DES]] | ||
| , | , | ||
| - | RC4 [[https://tools.ietf.org/html/rfc2246#ref-RC4 | RC4]], etc.) The keys for | + | RC4 [[https://tools.ietf.org/html/rfc2246#ref-RC4 | RC4]], etc.) The [[dido:public:ra:xapend:xapend.a_glossary:k:key|keys]] for |
| this symmetric encryption are generated uniquely for each | this symmetric encryption are generated uniquely for each | ||
| connection and are based on a secret negotiated by another | connection and are based on a secret negotiated by another | ||
| Line 41: | Line 41: | ||
| : //The TLS Record Protocol is used for encapsulation of various higher | : //The TLS Record Protocol is used for encapsulation of various higher | ||
| level protocols. One such encapsulated protocol, the TLS Handshake | level protocols. One such encapsulated protocol, the TLS Handshake | ||
| - | Protocol, allows the server and [[dido:public:ra:xapend:xapend.a_glossary:c:client|client]] to authenticate each other and | + | Protocol, allows the [[dido:public:ra:xapend:xapend.a_glossary:s:server|server]] and [[dido:public:ra:xapend:xapend.a_glossary:c:client|client]] to authenticate each other and |
| to negotiate an encryption algorithm and cryptographic keys before | to negotiate an encryption algorithm and cryptographic keys before | ||
| the application protocol transmits or receives its first byte of | the application protocol transmits or receives its first byte of | ||
| Line 48: | Line 48: | ||
| * //The peer's identity can be authenticated using asymmetric, or | * //The peer's identity can be authenticated using asymmetric, or | ||
| - | public key, cryptography (e.g., RSA [[https://tools.ietf.org/html/rfc2246#ref-RSA | RSA]], | + | [[dido:public:ra:xapend:xapend.a_glossary:p:public_key|public key]], cryptography (e.g., RSA [[https://tools.ietf.org/html/rfc2246#ref-RSA | RSA]], |
| DSS [[https://tools.ietf.org/html/rfc2246#ref-DSS | DSS]], etc.). This | DSS [[https://tools.ietf.org/html/rfc2246#ref-DSS | DSS]], etc.). This | ||
| [[dido:public:ra:xapend:xapend.a_glossary:a:authentication|authentication]] can be made optional, but is generally required | [[dido:public:ra:xapend:xapend.a_glossary:a:authentication|authentication]] can be made optional, but is generally required | ||
dido/public/ra/xapend/xapend.b_stds/tech/ietf/tls.1628269640.txt.gz · Last modified: 2021/08/06 13:07 by murphy
