1998
DOI: 10.17487/rfc2404
|View full text |Cite
|
Sign up to set email alerts
|

The Use of HMAC-SHA-1-96 within ESP and AH

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
25
0

Year Published

1998
1998
2013
2013

Publication Types

Select...
8
1

Relationship

0
9

Authors

Journals

citations
Cited by 105 publications
(26 citation statements)
references
References 1 publication
0
25
0
Order By: Relevance
“…The host registration request message is authenticated by the host signature, which also protects the AA from impersonation attacks. After verifying the host authenticity (by getting the host record from the HNR through the hostname resolution procedure as explained earlier), the AA selects an appropriate integrity-check algorithm, which may be HMAC-SHA1 [11]. The AA also assigns an access ID (accessID) and an accessKey (which has a definite lifetime) and replies the host with a host registration response, containing the accessKey encrypted by the host's PK and the whole message signed by the AA.…”
Section: Network Access Securitymentioning
confidence: 99%
“…The host registration request message is authenticated by the host signature, which also protects the AA from impersonation attacks. After verifying the host authenticity (by getting the host record from the HNR through the hostname resolution procedure as explained earlier), the AA selects an appropriate integrity-check algorithm, which may be HMAC-SHA1 [11]. The AA also assigns an access ID (accessID) and an accessKey (which has a definite lifetime) and replies the host with a host registration response, containing the accessKey encrypted by the host's PK and the whole message signed by the AA.…”
Section: Network Access Securitymentioning
confidence: 99%
“…The inter-FA ICMP messages (solicitations and advertisements) MUST be authenticated and integrity protected using ESP [10]. The default ESP authentication algorithm for use in this specification is HMAC-SHA1-96 [12]. The absence of this security would allow denial-of-service attacks from malicious nodes at any distance from the FA.…”
Section: Generalized Link Layer and Ipv4 Address (Lla) Extensionmentioning
confidence: 99%
“…For example, HMAC-MD5 specified in RFC 2085 (Oehler and Glenn, 1997) recommends the support of long key lengths. However, in RFC 2403 (Madson and Glenn, 1998a), RFC 2404 (Madson and Glenn, 1998b), and RFC 2857 (Keromytis and Provos, 2000), the key size is restricted to 128 bits for HMAC-MD5 and 160 bits for each of HMAC-SHA-1 and HMAC-RIPEMD-160. Therefore, we implemented another version of the HMAC unit using a key size of 160 bits.…”
Section: Hmac Implementation For Fixed Key Sizementioning
confidence: 99%
“…There exists a number of standardized authentication algorithms using HMAC. The most popular ones are HMAC-MD5 (Madson and Glenn, 1998a), HMAC-SHA-1 (Madson and Glenn, 1998b), and HMAC-RIPEMD-160 (Keromytis and Provos, 2000).…”
Section: Introductionmentioning
confidence: 99%