#14: Support longer wrapped keys than OAEP allows
Comment (by [email protected]): As pointed out by James Manger in http://www.ietf.org/mail- archive/web/jose/current/msg01853.html, "Keys for all of the algorithms fit within OAEP with a 2048-bit RSA key. JWA already says RSA key sizes MUST be at least 2048 bits. This already looks sufficient." I agree with James that I know of no use case where this limit will be hit in practice. However it could be that Richard is thinking of encrypting JWKs, rather than wrapping keys, in which case we already have a solution in the form of draft-miller-jose-jwe-protected-jwk. Also, see my comments at http://trac.tools.ietf.org/wg/jose/trac/ticket/13#comment:2 on the desirability of distinguishing between (1) Encrypting the ephemeral symmetric key value used within a JWE and (2) encrypting a JWK or JWK Set containing symmetric and/or private key information and potentially other key attributes, enabling the encrypted JWK or JWK Set to be safely stored or transported. Finally, as Matt Miller wrote in http://www.ietf.org/mail- archive/web/jose/current/msg01863.html, "Personally, I don't think it's worth discussing this much further without a more complete counter- proposal on the table." I agree that a concrete set of proposed changes would be needed to make this actionable. -- -------------------------+------------------------------------------------- Reporter: [email protected] | Owner: draft-ietf-jose-json-web- Type: defect | [email protected] Priority: major | Status: new Component: json-web- | Milestone: encryption | Version: Severity: - | Resolution: Keywords: | -------------------------+------------------------------------------------- Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/14#comment:2> jose <http://tools.ietf.org/jose/> _______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
