RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

RFC 4868, "Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 with IPsec", May 2007

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: sec

Errata ID: 1785
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Sheila Frankel
Date Reported: 2009-05-19
Verifier Name: Pasi Eronen
Date Verified: 2009-05-27

Section 2.7.2.3 says: 

Test Case AUTH512-4:
   Key =          0a0b0c0d0e0f10111213141516171819
                  0102030405060708090a0b0c0d0e0f10
                  1112131415161718191a1b1c1d1e1f20
                  2122232425262728292a2b2c2d2e2f30
                  3132333435363738393a3b3c3d3e3f40  (64 bytes)

It should say:

Test Case AUTH512-4:
   Key =          0102030405060708090a0b0c0d0e0f10
                  1112131415161718191a1b1c1d1e1f20
                  2122232425262728292a2b2c2d2e2f30
                  3132333435363738393a3b3c3d3e3f40  (64 bytes)

Notes:

Originally noted by Tero Kivinen

Status: Reported (1)

RFC 4868, "Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 with IPsec", May 2007

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: sec

Errata ID: 5507
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: f. Le Pouliquen
Date Reported: 2018-09-27

Section 2.7.2.2. says: 

Test Case AUTH384-4:
   Key =          0102030405060708090a0b0c0d0e0f10
                  1112131415161718191a1b1c1d1e1f20
                  0a0b0c0d0e0f10111213141516171819

It should say:

Test Case AUTH384-4:
   Key =          0102030405060708090a0b0c0d0e0f10
                  1112131415161718191a1b1c1d1e1f20
                  2122232425262728292a2b2c2d2e2f30

Notes:

as the keys increase from case 256 to 384 and to 512, they have the same base.

Report New Errata



Advanced Search