ACTION-297: Propose change to 1.1 to address issue-105
Propose change to 1.1 to address issue-105
- State:
- closed
- Person:
- Konrad Lanz
- Due on:
- May 20, 2009
- Created on:
- May 13, 2009
- Associated Issue:
- ISSUE-105
- Related emails:
- Agenda: Distributed Meeting 2009-12-15 (from frederick.hirsch@nokia.com on 2009-12-14)
- HMAC output length erratum for XML Signature 1.0 (Re: Is ACTION-297 the impact of ISSUE-105 (HMAC output length is defined on bits base64 on octets) on the XMLDSig 1.0 errata ? (see also: ACTION-298 and ACTION-320)) (from tlr@w3.org on 2009-12-07)
- Minutes 13 October2009 (from brich@us.ibm.com on 2009-10-13)
- Agenda: Distributed Meeting 2009-10-13 (from frederick.hirsch@nokia.com on 2009-10-09)
- Re: Agenda: Distributed Meeting 2009-10-06 (from Konrad.Lanz@iaik.tugraz.at on 2009-10-06)
- Agenda: Distributed Meeting 2009-10-06 (from frederick.hirsch@nokia.com on 2009-10-02)
- Re: Sept 29 Meeting Minutes (from Frederick.Hirsch@nokia.com on 2009-09-29)
- Agenda: Distributed Meeting 2009-09-29 (from frederick.hirsch@nokia.com on 2009-09-28)
- Agenda: Distributed Meeting 2009-09-22 v2 (from frederick.hirsch@nokia.com on 2009-09-18)
- Draft minutes for Sep 8 (from cantor.2@osu.edu on 2009-09-08)
- Is ACTION-297 the impact of ISSUE-105 (HMAC output length is defined on bits base64 on octets) on the XMLDSig 1.0 errata ? (see also: ACTION-298 and ACTION-320) (from Konrad.Lanz@iaik.tugraz.at on 2009-09-08)
- F2F Minutes updated - revision for approval (from frederick.hirsch@nokia.com on 2009-06-02)
- Draft minutes from May 13 (from pratik.datta@oracle.com on 2009-05-21)
Related notes:
In XMLDSIG 1.0 (second Edition) it is unclear how a HMACOutputLength that is not divisible by 8 should be handeled/padded. In XMLDSIG 1.1 only HMACOutputLength divisible by 8 are allowed.
XMLDISG 1.0: For legacy reasons shouldn't we also be able to work with HMACOutputLength not divisible by 8.
erratum is accepted and published.
Thomas Roessler, 14 Dec 2009, 13:51:50Display change log.