Difference between revisions of "Hash-based message authentication code (HMAC)"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 10: | Line 10: | ||
* [[Terraform provider: dns]]: <code>[[hmac-md5]]</code> | * [[Terraform provider: dns]]: <code>[[hmac-md5]]</code> | ||
* [[OATH]] | * [[OATH]] | ||
| + | * [[HTTP Message Signatures]] | ||
| + | * [[HMAC-SHA256]] | ||
| + | * [[JWT]] | ||
== See also == | == See also == | ||
Latest revision as of 14:14, 4 April 2024
wikipedia:HMAC is used to verify data integrity and authenticity of a message using a cryptographic hash function and a secret cryptographic key.
HMAC is used within the IPsec, SSH and TLS protocols and for JSON Web Tokens.
TLS Error: cannot locate HMAC in incoming packet from [AF_INET6]::ffff:10.156.0.97:45318
Related[edit]
- Webhook
- HMAC API from AWS Key Management Service
- Terraform provider: dns:
hmac-md5 - OATH
- HTTP Message Signatures
- HMAC-SHA256
- JWT
See also[edit]
- Cypher: Hash, MD5, SHA, Bcrypt, Blowfish, HMAC, Equihash, Argon2
- Authentication, AAA, MFA, OpenID, OAuth, OATH, PAM, Personal access token, CWE: Broken Access Control, PAT, Mutual authentication, Federated authentication, IdP, Amazon Cognito, Phone to sign in, Firebase Authentication, Auth0, WebAuthn, Web3auth, Challenge-response, Passwordless authentication, HMAC, HOTP, TOTP, OATH
Advertising:
