[jira] [Comment Edited] (CXF-6728) Review and improve the way EC keys are handled in JOSE code

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Comment Edited] (CXF-6728) Review and improve the way EC keys are handled in JOSE code

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/CXF-6728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890298#comment-15890298 ]

Sergey Beryozkin edited comment on CXF-6728 at 5/15/17 9:21 AM:
----------------------------------------------------------------

The following paper showing the EC leaks (reported by Antonio) needs to be checked a bit later on and then we can close this issue

https://research.google.com/pubs/pub45790.html
http://blog.intothesymmetry.com/2017/03/critical-vulnerability-in-json-web.html


was (Author: sergey_beryozkin):
The following paper showing the EC leaks (reported by Antonio) needs to be checked a bit later on and then we can close this issue

https://research.google.com/pubs/pub45790.html

> Review and improve the way EC keys are handled in JOSE code
> -----------------------------------------------------------
>
>                 Key: CXF-6728
>                 URL: https://issues.apache.org/jira/browse/CXF-6728
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAX-RS Security
>            Reporter: Sergey Beryozkin
>
> The code which decodes/encodes JOSE EC key outputs needs to be reviewed. The current code was meant to be a more optimal version of the code available in Jose4J (which is actually a slightly improved version of the code found in Santuario plus dealing with JOSE specific optimizations). This code needs to be double-checked and if needed reverted to a version closer to the one found in Jose4J.
> Curves: it should be possible to deduce the values from the current EC key as opposed to having users configure them explicitly.
> Next,
> https://tools.ietf.org/html/draft-ietf-jose-cfrg-curves-00
> has just come out, so I guess EC code will need to be updated accordingly.
> I also recall that if EC keys are loaded from JKS then the default algorithm needs be set correctly if EC signature/enc algo is not set, at the moment it is always set to RS256 by default



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)