-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug 27814 - Section A.2 - the usage mapping of "enc" is incorrect #77
Comments
I'm not sure there was a conclusion to the very long discussion on the original bug back in January 2015. Given that JOSE uses the |
I'm also not sure A.2 is useful. Perhaps we should remove it ? |
I do not believe there was any final decision to do something from the last discussion. I would tend to agree that removing A.2 is not a harmful operation. I am in favor of any thing that makes the usage of JWK structures here better match that of the IETF specification. |
In the absence of further input, I will implement this by removing section A.2 and allowing the presence of the |
sounds good to me. |
LGTM. |
PR #114 |
PR #114 looks good to me. |
Bug 27814:
The text of A.2 says that
enc maps to ["encrypt", "decrypt", "wrapKey", "unwrapKey"]
however my reading of section 4.2 of the JWK specification (http://tools.ietf.org/html/draft-ietf-jose-json-web-key-39#section-4.2) as well as the example in Appendix A.2 say that for keys of type "EC" the value of enc is correct. This means that the mapping should be
enc maps to ["encrypt", "decrypt", "wrapKey", "unwrapKey", "deriveBits", "deriveKey"]
This also changes the algorithm for importing of ECDH keys when using a jwk format. (No changes are needed for Diffie-Hellman because it does not support a jwk format.)
The text was updated successfully, but these errors were encountered: