⌕ Поиск по атласу

IETF · RFC · RFC2104

RFC2104 · HMAC: Keyed-Hashing for Message Authentication

HMAC: Keyed-Hashing for Message Authentication

This document describes HMAC, a mechanism for message authentication using cryptographic hash functions. HMAC can be used with any iterative cryptographic hash function, e.g., MD5, SHA-1, in combination with a secret shared key. The cryptographic strength of HMAC depends on the properties of the underlying hash function. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind

Официальная английская аннотация

This document describes HMAC, a mechanism for message authentication using cryptographic hash functions. HMAC can be used with any iterative cryptographic hash function, e.g., MD5, SHA-1, in combination with a secret shared key. The cryptographic strength of HMAC depends on the properties of the underlying hash function. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind

Связи документа

updated_by: RFC6151

Официальный источник · 1997-02-01

Полные импортированные сведения карточки
{
  "id": "RFC2104",
  "number": 2104,
  "title_en": "HMAC: Keyed-Hashing for Message Authentication",
  "title_ru": "",
  "summary_ru": "",
  "purpose_ru": "",
  "use_ru": "",
  "full_translation_path": "",
  "full_translation_checked_at": "",
  "full_translation_source_sha256": "",
  "architect_note_ru": "",
  "topics_ru": [],
  "translation_state": "not_prepared",
  "verification_level": "not_prepared",
  "verification_level_ru": "Русская выжимка не подготовлена",
  "verification_note_ru": "",
  "abstract_en": "This document describes HMAC, a mechanism for message authentication using cryptographic hash functions. HMAC can be used with any iterative cryptographic hash function, e.g., MD5, SHA-1, in combination with a secret shared key. The cryptographic strength of HMAC depends on the properties of the underlying hash function. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind",
  "authors": [
    "H. Krawczyk",
    "M. Bellare",
    "R. Canetti"
  ],
  "organizations": [],
  "publication_date": "1997-02-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "sec",
  "area_ru": "Безопасность",
  "working_group": "ipsec",
  "source_draft": "draft-ietf-ipsec-hmac-md5-00",
  "page_count": 11,
  "doi": "10.17487/RFC2104",
  "keywords": [
    "ipsec",
    "Message",
    "Digest",
    "Internet",
    "Protocol",
    "Security",
    "encryption"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [
      "RFC6151"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc2104/",
    "html": "https://www.rfc-editor.org/rfc/rfc2104.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc2104.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc2104/"
  }
}