diff options
Diffstat (limited to 'libxmlsec')
| -rw-r--r-- | libxmlsec/makefile.mk | 7 | ||||
| -rw-r--r-- | libxmlsec/readme.txt | 2 |
2 files changed, 4 insertions, 5 deletions
diff --git a/libxmlsec/makefile.mk b/libxmlsec/makefile.mk index 8b4568fb016e..495427c546ac 100644 --- a/libxmlsec/makefile.mk +++ b/libxmlsec/makefile.mk @@ -46,21 +46,20 @@ XMLSEC1VERSION=1.2.14 TARFILE_NAME=$(PRJNAME)-$(XMLSEC1VERSION) -#xmlsec1-configure.patch: Set up the build. Straightforward -#configuration +#xmlsec1-configure.patch: Set up the build. Straightforward configuration #xmlsec1-olderlibxml2.patch: Allow build against older libxml2, for macosx +#xmlsec1-nssdisablecallbacks.patch: Disable use of smime3 so don't need to package it #xmlsec1-customkeymanage.patch: Could we do this alternatively outside xmlsec #xmlsec1-nssmangleciphers.patch: Dubious, do we still need this ? -#xmlsec1-nssdisablecallbacks.patch: Dubious, do we still need this ? #xmlsec1-noverify.patch: As per readme.txt. #xmlsec1-mingw32.patch: Mingw32 support. #xmlsec1-mingw-customkeymanage-addmscrypto.patch builds the custom keymanager on mingw PATCH_FILES=\ xmlsec1-configure.patch \ xmlsec1-olderlibxml2.patch \ + xmlsec1-nssdisablecallbacks.patch \ xmlsec1-customkeymanage.patch \ xmlsec1-nssmangleciphers.patch \ - xmlsec1-nssdisablecallbacks.patch \ xmlsec1-noverify.patch \ xmlsec1-mingw32.patch \ xmlsec1-mingw-keymgr-mscrypto.patch diff --git a/libxmlsec/readme.txt b/libxmlsec/readme.txt index b518c6222687..55c6976f51f3 100644 --- a/libxmlsec/readme.txt +++ b/libxmlsec/readme.txt @@ -22,7 +22,7 @@ for details. There is a flag XMLSEC_KEYINFO_FLAGS_X509DATA_DONT_VERIFY_CERTS that can be set in a xmlSecKeyInfoCtx (see function xmlSecNssKeyDataX509XmlRead, in file -src/nss/x509.c), which indicates that one can turn of the validation. However, +src/nss/x509.c), which indicates that one can turn off the validation. However, setting it will cause that the validation key is not found. If the flag is set, then the key is not extracted from the certificate store which contains all the certificates of the X509Data elements. In other words, the certificates which |