RFC Errata
Found 12 records.
Status: Verified (8)
RFC 4758, "Cryptographic Token Key Initialization Protocol (CT-KIP) Version 1.0 Revision 1", November 2006
Source of RFC: IETF - NON WORKING GROUPArea Assignment: sec
Errata ID: 714
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-01-01
Verifier Name: Magnus Nystrom
Date Verified: 2007-01-05
Section 3.8.2 says:
</xs:sequence>
<xs:attribute name="id" type="xs:ID"/>
</xs:complexType>
It should say:
</xs:sequence>
</xs:complexType>
Notes:
from pending
Errata ID: 718
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-01-01
Verifier Name: Magnus Nystrom
Date Verified: 2007-01-05
Section 3.8.3 says:
<xs:attribute name=3D"Version" type=3D"ct-kip:VersionType"/>
</xs:complexType>
It should say:
<xs:attribute name=3D"Version" type=3D"VersionType"/>
</xs:complexType>
Notes:
from pending
Errata ID: 720
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-01-01
Verifier Name: Magnus Nystrom
Date Verified: 2007-01-05
Section 3.9.3 says:
<xs:complexContent>
<xs:extension base=3D"ExtensionType">
<xs:sequence>
It should say:
<xs:complexContent>
<xs:extension base=3D"AbstractExtensionType">
<xs:sequence>
Notes:
from pending
Errata ID: 722
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-01-01
Verifier Name: Magnus Nystrom
Date Verified: 2007-01-05
Appendix A says:
<xs:complexType name=3D"PayloadType">
<xs:annotation>
<xs:documentation xml:lang=3D"en">
</xs:documentation>
</xs:annotation>
It should say:
<xs:complexType name=3D"PayloadType">
<xs:annotation>
<xs:documentation xml:lang=3D"en">
Currently, only the nonce is defined. In future versions,
other payloads may be defined, e.g., for one-roundtrip
initialization protocols.
</xs:documentation>
</xs:annotation>
Notes:
documentation was missing
from pending
Errata ID: 723
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-01-01
Verifier Name: Magnus Nystrom
Date Verified: 2007-01-05
Appendix B.2 says:
<CT-KIPTrigger
xmlns=3D [...]
It should say:
<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<CT-KIPTrigger
xmlns=3D [...]
Notes:
from pending
Errata ID: 724
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-01-01
Verifier Name: Magnus Nystrom
Date Verified: 2007-01-05
Appendix B.4 says:
<ServerHello
xmlns=3D
"http://www.rsasecurity.com/rsalabs/otps/schemas/2005/12/ct-kip#"
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#"
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"
Version=3D"1.0" SessionID=3D"4114" Status=3D"Success">
It should say:
<ServerHello
xmlns=3D
"http://www.rsasecurity.com/rsalabs/otps/schemas/2005/12/ct-kip#"
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#"
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"
Version=3D"1.0" SessionID=3D"4114" Status=3D"Continue">
Notes:
from pending
Errata ID: 725
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-01-01
Verifier Name: Magnus Nystrom
Date Verified: 2007-01-05
Appendix D says:
n = ROUND( dsLen / bLen )
It should say:
n = CEILING( dsLen / bLen )
Notes:
Appendix D repeatedly uses the "ROUND" function where in fact it
should use the "CEILING function (3 instances: on pp. 49, 51, and 52).
from pending
Errata ID: 713
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-01-01
Verifier Name: Magnus Nystrom
Date Verified: 2007-01-05
Section 3.7.1 says:
The XML format for CT-KIP messages have been designed to be extensible. [...]
It should say:
The XML format for CT-KIP messages has been designed to be extensible. [...]
Notes:
from pending
Status: Reported (4)
RFC 4758, "Cryptographic Token Key Initialization Protocol (CT-KIP) Version 1.0 Revision 1", November 2006
Source of RFC: IETF - NON WORKING GROUPArea Assignment: sec
Errata ID: 5628
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Conrad Meyer
Date Reported: 2019-02-09
Section 3.5 says:
K_TOKEN = CT-KIP-PRF (R_C, "Key generation" || k || R_S, dsLen)
It should say:
K_TOKEN = CT-KIP-PRF (R_C, k || "Key generation" || R_S, dsLen)
Notes:
Here the RFC is simply incorrect w.r.t. the reference implementation (RSA's proprietary software).
The corrected text matches the reference implementation.
There are several more errata along these lines. With (all) the corrections, it becomes possible to implement 3rd party RFC4758 clients and servers that interact correctly with RSA clients and servers from the RFC text.
Errata ID: 5629
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Conrad Meyer
Date Reported: 2019-02-09
Section 3.8.6 says:
MAC = CT-KIP-PRF (K_AUTH, "MAC 2 computation" || R_C, dsLen)
It should say:
MAC = CT-KIP-PRF (K_AUTH, "MAC 2 Computation" || R_C, dsLen)
Notes:
Note the capitalization of the "C" in "Computation."
Here the RFC is simply incorrect w.r.t. the reference implementation (RSA's proprietary software); the corrected text matches the reference implementation.
Errata ID: 5630
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Conrad Meyer
Date Reported: 2019-02-09
Section D.2.2 says:
F (k, s, i) = OMAC1-AES (k, INT (i) || s)
It should say:
F (k, s, i) = OMAC1-AES (k, s || INT (i))
Notes:
The corrected text matches the (only) reference implementation; the RFC text does not.
Errata ID: 5631
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Conrad Meyer
Date Reported: 2019-02-09
Section D.2.1 says:
For tokens supporting this realization of CT-KIP-PRF, the following URI may be used to identify this algorithm in CT-KIP: http://www.rsasecurity.com/rsalabs/otps/schemas/2005/12/ ct-kip#ct-kip-prf-aes
It should say:
For tokens supporting this realization of CT-KIP-PRF, either of the following URIs may be used to identify this algorithm in CT-KIP: http://www.rsasecurity.com/rsalabs/otps/schemas/2005/12/ ct-kip#ct-kip-prf-aes http://www.rsasecurity.com/rsalabs/otps/schemas/2005/11/ ct-kip#ct-kip-prf-aes
Notes:
It seems some versions of the reference implementation use the 2005/11 date and some the 2005/12 one. Both refer to the same PRF construction.