Shibboleth Service Provider Security Advisory [17 March 2021] - backporting

Cantor, Scott cantor.2 at osu.edu
Wed Mar 17 16:18:39 GMT 2021


On 3/17/21, 12:13 PM, "Ferenc Wagner,,, on behalf of wferi at niif.hu" <wferi at niif.hu> wrote:

>    while leaving the version attribute of the <schema> element at 3.0?

The schema version isn't normative, I just update it to track the minor versions that add things to it. Schema versioning in general was....not a well thought out concept.

>    When is this schema file used?

The configuration is always validated when it's parsed. What I did *not* do was add it to the 2.x legacy schema, but the setting still "exists", logically, it just can't be turned back on with the old file namespace.

>    The changes to the 4 .cpp files applied cleanly, I think that's all
>    there is to do, right?

Yes, it's not a complex change. Whether it actually breaks somebody's system remains to be seen, I can't remember why on earth the feature existed.

-- Scott




More information about the Pkg-shibboleth-devel mailing list