path: root/external/libxmlsec/xmlsec1-vc.patch.1
AgeCommit message (Collapse)AuthorFilesLines
2017-09-15consistent naming of externals: libxmlsec -> xmlsecMichael Stahl1-29/+0
Change-Id: I9774dbec91b397d291d8f7f9bf96bbb75fc2baad Reviewed-on: Tested-by: Jenkins <> Reviewed-by: Michael Stahl <>
2017-09-15consistent naming of externals: xml2 -> libxml2Michael Stahl1-1/+1
Change-Id: Ia1164c70d02dce70cb346c1fd4033f12d91c6e5d Reviewed-on: Reviewed-by: Michael Stahl <> Tested-by: Michael Stahl <>
2017-06-14xmlsec: drop vc9 hunk from xmlsec1-vc.patch.1Miklos Vajna1-13/+0
This was added in commit 36ad473eeeace151af341869b0436fac8b1bdd2e (Build fixes for VC++ 10, 2010-10-20) where it was only safe to conditionally add support for Visual Studio 2010. Change-Id: I62c4aefd39a5943259a5a1e462f4762c1aac5e1e Reviewed-on: Tested-by: Jenkins <> Reviewed-by: Miklos Vajna <>
2017-05-10Upgrade libxmlsec to 1.2.24Miklos Vajna1-7/+9
Upstream changes interesting for us: - Added ECDSA-SHA1, ECDSA-SHA256, ECDSA-SHA512 support for xmlsec-nss, so we can drop 2 patches - Fixed XMLSEC_KEYINFO_FLAGS_X509DATA_DONT_VERIFY_CERTS handling, which allows dropping xmlsec1-noverify.patch.1 in the future Also backport a patch from xmlsec master that fixes signature creation on Windows (the release regressed in this regard). Change-Id: I2c14328283bf7d4f8af5595ea4c1efc29ee81f9e
2016-11-04Upgrade libxmlsec to 1.2.23Miklos Vajna1-4/+4
Obsoletes xmlsec1-win32-fix-undeclared.patch.1. Change-Id: I11cd52aebbe5ab224de9ab00b74c02abb46296f6 Reviewed-on: Tested-by: Jenkins <> Reviewed-by: Miklos Vajna <>
2016-07-27libxmlsec: mark part of xmlsec1-vc.patch.1 as upstreamedMiklos Vajna1-9/+0
Change-Id: I4a8365c98eef87274ae1809047fd4ea582102f0b Reviewed-on: Reviewed-by: Miklos Vajna <> Tested-by: Jenkins <>
2016-07-14Upgrade libxmlsec to 1.2.22Miklos Vajna1-6/+6
No major changes for us, except that finally we bundle the latest upstream (but still heavily patch it). Change-Id: I6bcfcdf48ec5d25eb3f7b14c89838942b4a11b48 Reviewed-on: Reviewed-by: Miklos Vajna <> Tested-by: Jenkins <>
2016-07-08Upgrade libxmlsec to 1.2.21Miklos Vajna1-9/+15
Obsoletes xmlsec1-ooxml.patch.1 and xmlsec1-vs2015.patch.1. Adds xmlsec1-keyinfo-revert.patch.1 till the LO side is adapted to the new xmlsec requirements. Change-Id: I1a46ad8fd7e9c8b4fa7a97591a1d90922969393d Reviewed-on: Tested-by: Jenkins <> Reviewed-by: Miklos Vajna <>
2016-04-20libxmlsec: split the upstreamed part of xmlsec1-vc.patch.1 into a new patchMiklos Vajna1-39/+0
Change-Id: I1a6201a21cdf3a42475487a42cd80d11cd5e42b6 Reviewed-on: Reviewed-by: Miklos Vajna <> Tested-by: Jenkins <>
2016-04-06Upgrade libxmlsec to 1.2.19Miklos Vajna1-4/+4
Obsoletes our xmlsec1-1.2.14-ansi.patch.1 and xmlsec1-android.patch.1. Change-Id: Ic6499b1a79e3f5a6d94beb62c0c338789c782c86 Reviewed-on: Tested-by: Jenkins <> Reviewed-by: Miklos Vajna <>
2016-03-18Upgrade libxmlsec to 1.2.16Miklos Vajna1-5/+5
No instant drop of any of our patches this time, but a considerable amount of xmlsec1-customkeymanage.patch.1 is now redundant, as part of the key wrapper code is available in this upstream release for both mscrypto and nss. But that can be cleaned up in a separate follow-up commit. Change-Id: I197eaffe3a52f2f9c02af982872185e017965006 Reviewed-on: Tested-by: Jenkins <> Reviewed-by: Miklos Vajna <>
2016-03-10Upgrade libxmlsec to 1.2.15Miklos Vajna1-0/+82
The primary benefit is that this release supports sha256 out of the box, so we can drop xmlsec1-nss-sha256.patch.1 and xmlsec1-mscrypto-sha256.patch.1. Change-Id: I78606c02591ac8ae7e347b0faa510ae2483e3183 Reviewed-on: Tested-by: Jenkins <> Reviewed-by: Caolán McNamara <> Tested-by: Caolán McNamara <>