Search results
Jump to navigation
Jump to search
Page title matches
- A '''hashed message authentication code''' or '''HMAC''' is a [[cryptography | cryptographic]] technique for provid2 KB (313 words) - 05:49, 8 April 2024
- 12 bytes (1 word) - 19:00, 3 January 2009
- #REDIRECT [[Hashed message authentication code]]48 bytes (5 words) - 00:08, 1 March 2010
- 116 bytes (17 words) - 18:56, 3 January 2009
- | pagename = Hashed message authentication code | abc = Hashed message authentication code2 KB (232 words) - 22:42, 28 February 2010
- Auto-populated based on [[Special:WhatLinksHere/Hashed message authentication code]]. Needs checking by a human.618 bytes (78 words) - 17:06, 11 January 2010
Page text matches
- #REDIRECT [[Hashed message authentication code]]48 bytes (5 words) - 00:34, 2 November 2008
- #REDIRECT [[Hashed message authentication code]]48 bytes (5 words) - 00:08, 1 March 2010
- {{rpl|Hashed message authentication code}}568 bytes (59 words) - 09:03, 22 April 2024
- {{R|Hashed message authentication code}} {{Rpl|Hashed message authentication code}}1 KB (122 words) - 01:39, 2 March 2010
- {{r|hashed message authentication code}}177 bytes (20 words) - 18:54, 3 January 2009
- A '''hashed message authentication code''' or '''HMAC''' is a [[cryptography | cryptographic]] technique for provid2 KB (313 words) - 05:49, 8 April 2024
- | pagename = Hashed message authentication code | abc = Hashed message authentication code2 KB (232 words) - 22:42, 28 February 2010
- {{r|Hashed message authentication code}}597 bytes (79 words) - 11:25, 11 January 2010
- {{r|Hashed message authentication code}}854 bytes (123 words) - 01:07, 2 November 2008
- Auto-populated based on [[Special:WhatLinksHere/Hashed message authentication code]]. Needs checking by a human.618 bytes (78 words) - 17:06, 11 January 2010
- * (in most cases) use a [[hashed message authentication code]] and some additional shared keying material to authenticate messages3 KB (544 words) - 05:49, 8 April 2024
- {{r|Hashed message authentication code}}1 KB (132 words) - 14:31, 22 March 2024
- ...stream cipher]]s, [[public key]] encryption, [[digital signature]]s, and [[hashed message authentication code]]s — depend on [[cryptographic key]]s. '''None of these can be secure3 KB (459 words) - 05:49, 8 April 2024
- * Packets or messages are often authenticated with a [[hashed message authentication code]], for [[information security#integrity|data integrity protection]]. This p6 KB (903 words) - 05:49, 8 April 2024
- To resist an adversary takes a '''keyed hash''', a [[Hashed message authentication code]] or HMAC. Sender and receiver share a secret key; the sender hashes using16 KB (2,641 words) - 15:51, 8 April 2024
- ...stream cipher]]s, [[public key]] encryption, [[digital signature]]s, and [[hashed message authentication code]]s — depend on [[cryptographic key]]s. '''None of these can be secure ...of the original hash. '''To resist an adversary takes a keyed hash''', a [[hashed message authentication code]] or HMAC. Sender and receiver share a secret key; the sender hashes using28 KB (4,396 words) - 06:22, 16 December 2008
- : Yes, At least [[block cipher]], [[cryptographic hash]] and [[hashed message authentication code]] for IPsec, plus [[stream cipher]] to complete the set. I'm being bottom-u18 KB (2,759 words) - 06:36, 1 November 2008
- IPsec packet authentication is done with a [[Hashed Message Authentication Code]] or HMAC. This is not just a hash of the packet data, but a more complex o40 KB (6,219 words) - 05:49, 8 April 2024
- ...of the original hash. '''To resist an adversary takes a keyed hash''', a [[hashed message authentication code]] or HMAC. Sender and receiver share a secret key; the sender hashes using52 KB (8,332 words) - 05:49, 8 April 2024
- : There are related questions. I think policy would be to have [[Hashed message authentication code]] with a redirect from [[HMAC]]. Fine there, but are MD4 and MD5 exceptions58 KB (9,554 words) - 14:37, 18 March 2024