dido:public:ra:xapend:xapend.b_stds:tech:ietf:hmac
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:tech:ietf:hmac [2019/05/21 20:07] nick created |
dido:public:ra:xapend:xapend.b_stds:tech:ietf:hmac [2021/08/17 12:04] (current) murphy [Introduction] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======== RFC2104 - Keyed-Hashing for Message Authentication (HMAC) ========= | + | ===== RFC2104 - Keyed-Hashing for Message Authentication (HMAC) ===== |
| - | [[dido:public:stds:tech:ietf | return to the IETF Standards ]] | + | [[dido:public:ra:xapend:xapend.b_stds:tech:ietf:start| return to the IETF Standards ]] |
| <table> | <table> | ||
| Line 12: | Line 12: | ||
| </table> | </table> | ||
| - | : **Note**: The following is an excerpt from the official IETF RFC. It is provided here as a connivence and is not authoritative. Refer to the original document as the authoritative reference. | + | : **Note**: The following is an excerpt from the official IETF RFC. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference. |
| - | ====== Introduction ====== | + | ==== Introduction ==== |
| : //Providing a way to check the integrity of information transmitted | : //Providing a way to check the integrity of information transmitted | ||
| over or stored in an unreliable medium is a prime necessity in the | over or stored in an unreliable medium is a prime necessity in the | ||
| world of open computing and communications. Mechanisms that provide | world of open computing and communications. Mechanisms that provide | ||
| - | such integrity check based on a secret key are usually called | + | such integrity check based on a secret [[dido:public:ra:xapend:xapend.a_glossary:k:key|key]] are usually called |
| "message authentication codes" (MAC). Typically, message | "message authentication codes" (MAC). Typically, message | ||
| - | authentication codes are used between two parties that share a secret | + | [[dido:public:ra:xapend:xapend.a_glossary:a:authentication|authentication]] codes are used between two parties that share a secret |
| key in order to validate information transmitted between these | key in order to validate information transmitted between these | ||
| parties. In this document we present such a MAC mechanism based on | parties. In this document we present such a MAC mechanism based on | ||
| Line 45: | Line 45: | ||
| and for which code is freely and widely available.// | and for which code is freely and widely available.// | ||
| - | * //To preserve the original performance of the hash function without | + | * //To preserve the original [[dido:public:ra:xapend:xapend.a_glossary:p:performance|performance]] of the hash function without |
| incurring a significant degradation.// | incurring a significant degradation.// | ||
| Line 54: | Line 54: | ||
| underlying hash function.// | underlying hash function.// | ||
| - | * //To allow for easy replaceability of the underlying hash function in | + | * //To allow for easy [[dido:public:ra:xapend:xapend.a_glossary:r:replaceability|replaceability]] of the underlying hash function in |
| case that faster or more secure hash functions are found or | case that faster or more secure hash functions are found or | ||
| required.// | required.// | ||
| Line 81: | Line 81: | ||
| RSA Labs' CryptoBytes, Vol. 2 No. 2, Summer 1996. | RSA Labs' CryptoBytes, Vol. 2 No. 2, Summer 1996. | ||
| [[http://www.rsa.com/rsalabs/pubs/cryptobytes.html]] | [[http://www.rsa.com/rsalabs/pubs/cryptobytes.html]] | ||
| - | )). This | + | )). This attack and other currently known weaknesses of MD5 do not compromise |
| - | attack and other currently known weaknesses of MD5 do not compromise | + | |
| the use of MD5 within HMAC as specified in this document (see | the use of MD5 within HMAC as specified in this document (see | ||
| Dobb); however, SHA-1 appears to be a cryptographically stronger | Dobb); however, SHA-1 appears to be a cryptographically stronger | ||
| Line 88: | Line 87: | ||
| applications where the superior performance of MD5 is critical. In | applications where the superior performance of MD5 is critical. In | ||
| any case, implementers and users need to be aware of possible | any case, implementers and users need to be aware of possible | ||
| - | cryptanalytic developments regarding any of these cryptographic hash | + | cryptoanalytic developments regarding any of these cryptographic hash |
| functions, and the eventual need to replace the underlying hash | functions, and the eventual need to replace the underlying hash | ||
| function. (See section 6 for more information on the security of | function. (See section 6 for more information on the security of | ||
| Line 94: | Line 93: | ||
| + | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
| + | /* To add a discussion page to this page, comment out the line that says | ||
| + | ~~DISCUSSION:off~~ | ||
| + | */ | ||
| + | ~~DISCUSSION:on|Outstanding Issues~~ | ||
| + | ~~DISCUSSION:off~~ | ||
dido/public/ra/xapend/xapend.b_stds/tech/ietf/hmac.1558483639.txt.gz · Last modified: 2019/05/21 20:07 by nick
