Up to [cvs.NetBSD.org] / pkgsrc / security / xml-security-c
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
Upgrade the Shibboleth SP software to version 3.5.0[.1], to address the recent critical security issue in the OpenSAML library. The Shibboleth release notes, edited to remove references to specific package systems, are as follows: ======================================================================== 3.5.0.1 (March 13, 2025) This is a service release to deliver the OpenSAML 3.3.1 library update, which addresses a critical vulnerability in the SP software. [ https://shibboleth.net/community/advisories/secadv_20250313.txt ] 3.5.0 (October 16, 2024) This is a small update to address a few bugs, update a number of libraries, and implement a correction to the default signing algorithm used when issuing signed requests via the SAML POST binding. This was inadvertently still defaulting to RSA-SHA1 and should have been using RSA-SHA256. There is the unlikely possibility of this causing interoperability issues with badly out of date Identity Providers, so is another reason for releasing it as a minor update. Those impacted are free to override the signing algorithm as documented. This release is accompanied by an update to Xerces-C V3.3.0, OpenSAML V3.3.0, and a new fork of the now-retired Santuatio XML-Security library which has been maintained by the project for many years and is now a local fork of that code with large portions removed, released as V3.0.0. 3.4.1 (January 10, 2023) This is a small patch to address a few bugs, in particular: Reinforcing the xmltooling library (V3.2.3, included in this Windows release) to block an unnecessary XML Encryption construct, related to the advisory issued for the IdP recently. The SP is not believed to be vulnerable, but this is a defensive measure. A warning has been added to the log when systems do not configure an explicit value for the redirectLimit setting. The default for this setting remains liberal for compatibility, so the warning was requested to highlight that fact. 3.4.0 (November 3, 2022) This is a minor update containing a new setting suggested by a contributor (thus the unplanned minor version change) controlling retries when TCP connections to shibd are used. The other changes are minimal in nature. 3.3.0 (November 30, 2021) This is a minor update that contains a small number of fixes, one small feature addition, and a number of additional deprecation warnings for at risk features. This version also introduces changes to the supported platforms and to the packaging process. This is expected to be the final feature update to the SP in its current form with the project's focus shifting to radical redesign. Deprecations Deprecations are now handled with a common "Shibboleth.DEPRECATION" logging category for easier identification. While deprecating a feature does not guarantee it will be removed and not deprecating something does not guarantee its continued support, we have tried to identify the most likely features that are at risk during the redesign process that will occur before a V4 is available. 3.2.3 (July 6, 2021) This is a patch update that fixes a regression in the RequestMap implementation introduced in V3.2.0. Earlier versions are not impacted by this bug but are of course subject to critical vulnerabilities so this is now the only safe version to use. 3.2.2 (April 25, 2021) This is a patch update that fixes a couple of bugs and addresses the security vulnerability described in this advisory. [ https://shibboleth.net/community/advisories/secadv_20210426.txt ] 3.2.1 (March 16, 2021) This is a patch update that fixes a couple of bugs and addresses the security vulnerability described in this advisory. [ https://shibboleth.net/community/advisories/secadv_20210317.txt ] 3.2.0 (December 14, 2020) This is a minor update that includes some minimal new functionality and addresses some bugs. Changes to Defaults The shipped default for the handlerSSL and cookieProps settings (see Sessions) is now to assume use of TLS because of the problems combining use of insecure cookies with SameSite. Upgrades are not impacted by this change, but all deployments will encounter problems going forward without TLS due to browser changes. A few configuration settings have been renamed as part of the project's broader push to eliminate insensitive language from the code and some new deprecation warnings may be observed.
xml-security-c: Update to 2.0.2. Patch from maya.
Changes:
2.0.0:
Bug
[SANTUARIO-496] - DSA verification crashes OpenSSL on invalid combinations of key content
2.0.1:
Bug
[SANTUARIO-491] - Default KeyInfo resolver doesn't check for empty element content.
2.0.0:
Bug
[SANTUARIO-382] - Unconditionally enable large file support
[SANTUARIO-418] - Invalid acceptance of unpadded RSA signatures
[SANTUARIO-435] - Automake misses the subdir-objects option
[SANTUARIO-437] - Cannot compile as C++11
[SANTUARIO-447] - XSECCryptoX509::loadX509PEM() can read past unterminated buffer
[SANTUARIO-449] - TXFMOutputFile can try to close unopened stream
[SANTUARIO-470] - dsig/DSIGReference.cpp:931: bad type ?
[SANTUARIO-471] - Patch for C++11 compile failures
[SANTUARIO-473] - Build failure using NSS
[SANTUARIO-474] - Better overflow checking
[SANTUARIO-479] - xml-security-cpp compilation errors
Improvement
[SANTUARIO-460] - Support for OpenSSL 1.1
[SANTUARIO-461] - Internal key store should be deleted on any CryptoAcquireContext() error
[SANTUARIO-472] - Conditional inclusion of XMKS code in library
[SANTUARIO-476] - Change default behavior for inferring attribute IDness by name
Changes 1.6.0: * Fix: wrong namespace in encryption DigestMethod * Fix: RetrievalMethod handler * Fix: support for >1 CRL per KeyInfo * Fix: buffer initialization issue * Fix: vector index bug * Fix: stylesheet append bug * Fix: header guard in XPath transform header * Fix: string release crash * Fix: improper c14n of XSLT * Fix: setters for Reference Type/Id * Fix: skip comments in X509Certificate elements * Fix: more header guards * Fix: NSS verification of RSA broken * Expose algorithm URI on Signature and Reference objects * White/blacklisting of otherwise registered algorithms * Add selected XML Signature 1.1 KeyInfo extensions * Add elliptic curve keys and signatures via ECDSA * Support debugging of Reference/SignedInfo data * Clean up tests for SHA2 algorithms in OpenSSL * Updated autoconf script, added NSS support, removed pre-automake material * Add methods for Reference removal to DSIGSignature/DSIGSignedInfo classes
Pullup ticket #2835 - requested hasso
xml-security-c: security update
Revisions pulled up:
- security/xml-security-c/Makefile 1.3
- security/xml-security-c/PLIST 1.3
- security/xml-security-c/distinfo 1.2
---
Module Name: pkgsrc
Committed By: hasso
Date: Fri Jul 24 20:33:16 UTC 2009
Modified Files:
pkgsrc/security/xml-security-c: Makefile PLIST distinfo
Log Message:
Update to 1.5.1. No detailed changelog, but from announcements:
1.5.1 release provides some bug fixes and a fix for the recently announced
HMAC vulnerability in the XML Signature specification (CVE-2009-0217).
1.5.0 release provides more bug fixes, partial support for Inclusive
Canonicalization 1.1, and support for the Xerces 3.x official release and
32/64-bit portability APIs.
Update to 1.5.1. No detailed changelog, but from announcements: 1.5.1 release provides some bug fixes and a fix for the recently announced HMAC vulnerability in the XML Signature specification (CVE-2009-0217). 1.5.0 release provides more bug fixes, partial support for Inclusive Canonicalization 1.1, and support for the Xerces 3.x official release and 32/64-bit portability APIs.
Remove @dirrm entries from PLISTs
XML Security is an C++ implementation of the W3C digital signature specification that makes it possible for programmers to create and validate signed XML documents.
Initial revision