I wanted to wait a little more before implementing that because the discussion here about it seems to bring too many changes to the code. There are other things too that need to be improved. But jsoncrypto implements all proposed alg and enc values other than none (which I find strange) and dir (which I had implemented first but the group at that time seemed to think that this might make it too easy for developers to use the same cek too often (always)).
-----Original Message----- From: Manger, James H [mailto:[email protected]] Sent: Thursday, August 02, 2012 3:26 AM To: Nennker, Axel; [email protected] Subject: RE: implementing JOSE in Java: jsoncrypto Axel, > I moved my JOSE implementation out of my openinfocard project into a > new repository: > https://code.google.com/p/jsoncrypto/ It is good to see another JOSE implementation. Does jsoncrypto implement the "MUST understand everything" rule? [JWE-05, section 4] Implementations MUST understand the entire contents of the header; otherwise, the JWE MUST be rejected. [JWE-05, section 6] 4. The resulting JWE Header MUST be validated to only include parameters and values whose syntax and semantics are both understood and supported. Jsoncrypto does not appear to implement this rule. It appears to take the obvious approach of looking in the header for the fields it needs -- and ignoring anything else that might be there. [Regardless of any possible merit in a "MUST understand everything" rule, the fact that it will often not be implemented seems like a really good reason to drop the rule so the spec reflects reality.] -- James Manger _______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
