You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by "Scott Cantor (Jira)" <ji...@apache.org> on 2021/10/14 18:32:00 UTC

[jira] [Updated] (SANTUARIO-513) Better Signature syntax enforcement

     [ https://issues.apache.org/jira/browse/SANTUARIO-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Cantor updated SANTUARIO-513:
-----------------------------------
    Affects Version/s: C++ 2.0.3

> Better Signature syntax enforcement
> -----------------------------------
>
>                 Key: SANTUARIO-513
>                 URL: https://issues.apache.org/jira/browse/SANTUARIO-513
>             Project: Santuario
>          Issue Type: Bug
>          Components: C++
>    Affects Versions: C++ 2.0.0, C++ 2.0.1, C++ 2.0.2, C++ 2.0.3
>            Reporter: Scott Cantor
>            Assignee: Scott Cantor
>            Priority: Major
>
> There's a bug in the Signature load routine that relates to a commented out check that was failing the load when unknown content appeared at the end of a Signature element.
> The code was unwisely changed to permit "non-conformant signatures", which is an absolutely indefensible decision. This is how you get security bugs. Non-conformant signatures can go right to hell.
> Adding an option to control this behavior is the absolute minimum we should do, but the default should be strict, and the rest of the load methods should be reviewed for any similar permissiveness.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)