[
https://issues.apache.org/jira/browse/WSS-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381216#comment-16381216
]
Willem Salembier commented on WSS-625:
--------------------------------------
Spec leads discussed about this here:
https://lists.w3.org/Archives/Public/w3c-ietf-xmldsig/2001AprJun/0183.html
The overall sentiment was to better remove the 76 length requirement and CRLF
ending to avoid c14n issues. The amendment was added to
https://www.w3.org/TR/xmlschema-2/#base64Binary
Still both forms are permitted and Base64 parsers should be permissive,. It’s
just odd to see & #13 characters in XML-DSIG Base64 elements
> Use RFC4648 base64 encoder for signature values and BST
> -------------------------------------------------------
>
> Key: WSS-625
> URL: https://issues.apache.org/jira/browse/WSS-625
> Project: WSS4J
> Issue Type: Bug
> Components: WSS4J Core
> Affects Versions: 2.2.1
> Reporter: Willem Salembier
> Assignee: Colm O hEigeartaigh
> Priority: Major
>
> The upgrade to JDK 8 Base64 RFC2045 mime encoder breaks our clients because
> all CR gets escaped to {{& #13;}}.
> {code}<ds:SignatureValue>ZizIuoDNc7Sn9wnvP6HC0NlouooLq2UdjOHcvGDkDPLjXnJgoVRgO5PTEfLJlNQErF6PWiMwL48d
> 2yCW5eop7aVHgSdL7o744Y4tb3nbQC48F8SIn64IR2XQsisF8wnpaz8krjOQWOFOzyznh3/xVyul
> lxiVVx0bTiIMWM9aQ4HKNUbLVfPxZxrQcbtduOioKzYfydJzEek3Z4/8GGMGERlYb5Wy/RHjzHkX
> TUz7l0Vg0bATDN3/lBwrwB1Aiu/79e+eURj5BFIwvveW/hjC1zcq2PqWzsx+2KP4zh+FIqtyk703
> PM/ahJpntuRoVR+dvDrfEKbMQK0TNswJoWtUjg==</ds:SignatureValue>
> {code}
> Can the behavior from version 2.1.12 be kept. Instead of
> {{Base64.getMimeEncoder()}} use {{Base64.getEncoder()}}
> Perhaps make it configurable
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
