Looks like the very last part of the example in JWA Appendix D* got overlooked in this change. It still has the base64url encoded representation of the derived key as usEpwFIC_qrmBExntFwxMA but I believe it should be VqqN6vgjbSBcIijNcacQGg
* http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-16#appendix-D On Sun, Sep 15, 2013 at 3:57 PM, Mike Jones <[email protected]>wrote: > ** ** > > One breaking change was made: When doing ECDH-ES key agreement, the > AlgorithmID value used in the KDF computation now has a length prefix. So > for instance, the representation of the “enc” value “A128GCM” is now > prefixed by the number 7, represented as a 32-bit big-endian value, when > used as the AlgorithmID value. (Such prefixes were already in place for > the other variable-length KDF parameters.)**** >
_______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
