Revision as of 06:48, 12 March 2023 edit Citation bot (talk \| contribs) Bots 5,869,232 edits Alter: template type. Add: s2cid, doi, date, newspaper, authors 1-7. Removed parameters. Some additions/deletions were parameter name changes. \| Use this bot. Report bugs. \| Suggested by Anderjef \| #UCB_toolbar ← Previous edit		Revision as of 14:46, 17 March 2023 edit undo 2.27.171.241 (talk) →Overview: Use IETF RFC template to make RFC links Next edit →
Line 7: == Overview == Digest access authentication was originally specified by ~~RFC~~{{IETF RFC\|2069}} (''An Extension to HTTP: Digest Access Authentication''). RFC 2069 specifies roughly a traditional digest authentication scheme with security maintained by a server-generated ''[[Cryptographic nonce\|nonce value]]''. The authentication response is formed as follows (where HA1 and HA2 are names of string variables): :<syntaxhighlight lang="text"> Line 17: An MD5 hash is a 16-byte value. The HA1 and HA2 values used in the computation of the response are the hexadecimal representation (in lowercase) of the MD5 hashes respectively. RFC 2069 was later replaced by ~~RFC~~{{IETF RFC\|2617}} (''HTTP Authentication: Basic and Digest Access Authentication''). RFC 2617 introduced a number of optional security enhancements to digest authentication; '''"quality of protection" (qop)''', nonce counter incremented by client, and a client-generated random nonce. These enhancements are designed to protect against, for example, [[chosen-plaintext attack]] [[cryptanalysis]]. If the algorithm directive's value is "MD5" or unspecified, then HA1 is

Digest access authentication: Difference between revisions