How is the ES512 example broken and what needs to be done to fix it?
Did you also verify that you can reproduce the key agreement result at
http://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-14#appendix-D?
I ask that because since it was published, three other implementations have
produced the key value usEpwFIC_qrmBExntFwxMA rather than
jSNmj9QK9ZGQJ2xg5_TJpA as published.
-- Mike
From: [email protected] [mailto:[email protected]] On Behalf Of Richard
Barnes
Sent: Thursday, August 15, 2013 4:47 PM
To: [email protected]
Subject: [jose] JOSE in Python
Hey all,
I've just pushed to GitHub a pretty complete JOSE library I've worked up in
Python.
<https://github.com/bifurcation/pyjose>
It supports pretty much all of the current specs, including:
-- JSON and compact serializations
-- Custom levels of header protection (all/none/some)
-- Multi-signer JWS and multi-recipient JWE
-- All JWA algorithms besides "none" (which should not be used anyway)
It successfully processes the examples in the current specs (except the "ES512"
one, which is broken), and successfully interoperates with itself in all 288
different configurations ("alg" + "enc" + "protected"). I have not yet tested
it against any other JOSE implementations.
I also took this opportunity to start up a list of implementations on the JOSE
wiki. Right now it's pretty short because I don't know of that many off the
top of my head.
<http://trac.tools.ietf.org/wg/jose/trac/wiki/WikiStart>
Comments / bugs welcome!
Thanks,
--Richard
_______________________________________________
jose mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/jose
