[jira] [Commented] (SANTUARIO-482) Provide a way to avoid using the RFC-2045 MIME encoder

["Willem Salembier (JIRA)" <ji...@apache.org>]

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

Willem Salembier commented on SANTUARIO-482:
--------------------------------------------

Wouldn’t it be more safe to invert the default? A fixed length limitation with CRLF line ending wasn’t the intention of the spec leads. To keep it compatible with 2.1.x I’d propose org.apache.xml.security.forceMimeEncoder (default false)


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 



> Provide a way to avoid using the RFC-2045 MIME encoder
> ------------------------------------------------------
>
>                 Key: SANTUARIO-482
>                 URL: https://issues.apache.org/jira/browse/SANTUARIO-482
>             Project: Santuario
>          Issue Type: Improvement
>            Reporter: Colm O hEigeartaigh
>            Assignee: Colm O hEigeartaigh
>            Priority: Major
>             Fix For: Java 2.1.2
>
>         Attachments: SANTUARIO-482.patch
>
>
> The XML Signature spec says that RFC-2045 (MIME) BASE-64 encoder must be used, and this is what Santuario 2.1.0 uses. However this is a break with our older Base64 usage, which did not include line breaks. There should be a way of setting a system property to avoid adding line breaks, and just using the RFC-4648 BASE-64 encoder.
>  
> The attached patch adds a new system property "org.apache.xml.security.ignoreMimeEncoder". If set to "true", then RFC-4648 is used for BASE-64 encoding (and hence no line breaks).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)