** Bug
* [CPPOST-91] - BOOST autoconf macros break with gcc5
Release Notes - OpenSAML 2 - C++ - Version 2.5.4
** Bug
* [CPPOST-87] - legacyOrgNames doesn't work as expected with empty
mdui:UIInfo
* [CPPOST-88] - Insufficient XML entity encoding in Metadata Status
generation
* [CPPOST-90] - Condition validation for empty element incorrectly
requires either a NotBefore or a NotOnOrAfter attribute
This is part of fixing PR pkg/50354
Problems found locating distfiles:
Package f-prot-antivirus6-fs-bin: missing distfile fp-NetBSD.x86.32-fs-6.2.3.tar.gz
Package f-prot-antivirus6-ws-bin: missing distfile fp-NetBSD.x86.32-ws-6.2.3.tar.gz
Package libidea: missing distfile libidea-0.8.2b.tar.gz
Package openssh: missing distfile openssh-7.1p1-hpn-20150822.diff.bz2
Package uvscan: missing distfile vlp4510e.tar.Z
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
Bugfixes
[CPPOST-83] - Compile error with boost 1.53
[CPPOST-86] - samlsign core dumps when -dig option is used
2.5.2:
(none)
2.5.1:
Bugfixes
[CPPOST-79] - Typo in "metadata intance failed manual validation checking"
log message
[CPPOST-80] - SAMLTIME_MAX constant breaks for universal Mac builds
Improvement
[CPPOST-78] - Add metadata:rpi schema to OpenSAML
2.5.0:
Bugfixes
[CPPOST-65] - Remove compile time version output where possible.
[CPPOST-70] - Problem calling virtual functions from base class constructors
[CPPOST-71] - Various clone methods are broken.
[CPPOST-75] - ChainingTrustEngine resets SOAP/TLS-based null peer entity name,
forces TrustEngine name matching
Improvements
[CPPOST-74] - metadata provider should check validity before replacing
old metadata
[CPPOST-76] - filter IdPs somehow that don't declare themselves "ready"
New Features
[CPPOST-69] - Load Folders of Metadata
[CPPOST-73] - Metadata filter that can add EntityAttribute tags
Bug
* Reload interval staying too low on reload failures.
* [HTTP-Redirect binding] [Message encoding] There should be no '%0A' in the
SAMLRequest parameter value
