summaryrefslogtreecommitdiff
path: root/libxmlsec
diff options
context:
space:
mode:
authorJens-Heiner Rechtien <hr@openoffice.org>2005-12-29 14:19:29 +0000
committerJens-Heiner Rechtien <hr@openoffice.org>2005-12-29 14:19:29 +0000
commit1da6b4d65b06080c30e3a4c40198663f2f53eed1 (patch)
treeef30ddf323d5dfc95436afab07d17a89727908b2 /libxmlsec
parent311c4faa1297b680fd0a67c5e3097426c4b4f7d6 (diff)
#i10000#: more C++ style comments in C file removed
Diffstat (limited to 'libxmlsec')
-rw-r--r--libxmlsec/xmlsec1-1.2.6.patch38
1 files changed, 19 insertions, 19 deletions
diff --git a/libxmlsec/xmlsec1-1.2.6.patch b/libxmlsec/xmlsec1-1.2.6.patch
index b430875..2a8398d 100644
--- a/libxmlsec/xmlsec1-1.2.6.patch
+++ b/libxmlsec/xmlsec1-1.2.6.patch
@@ -13178,27 +13178,27 @@
if (!CERT_LIST_END(head1, certs)) {
! continue;
}
-! //JL: OpenOffice.org implements its own certificate verification routine.
-! //The goal is to seperate validation of the signature
-! //and the certificate. For example, OOo could show that the document signature is valid,
-! //but the certificate could not be verified. If we do not prevent the verification of
-! //the certificate by libxmlsec and the verification fails, then the XML signature may not be
-! //verified. This would happen, for example, if the root certificate is not installed.
-! //
-! //In the store schould only be the certificate from the X509Certificate element
-! //and the X509IssuerSerial element. The latter is only there
-! //if the certificate is installed. Both certificates must be the same!
-! //In case of writing the signature, the store contains only the certificate that
-! //was created based on the information from the X509IssuerSerial element.
+! /* JL: OpenOffice.org implements its own certificate verification routine.
+! The goal is to seperate validation of the signature
+! and the certificate. For example, OOo could show that the document signature is valid,
+! but the certificate could not be verified. If we do not prevent the verification of
+! the certificate by libxmlsec and the verification fails, then the XML signature may not be
+! verified. This would happen, for example, if the root certificate is not installed.
+!
+! In the store schould only be the certificate from the X509Certificate element
+! and the X509IssuerSerial element. The latter is only there
+! if the certificate is installed. Both certificates must be the same!
+! In case of writing the signature, the store contains only the certificate that
+! was created based on the information from the X509IssuerSerial element. */
! status = SECSuccess;
! break;
-! // status = CERT_VerifyCertificate(CERT_GetDefaultCertDB(),
-! // cert, PR_FALSE,
-! // (SECCertificateUsage)0,
-! // timeboundary , NULL, NULL, NULL);
-! // if (status == SECSuccess) {
-! // break;
-! // }
+! /* status = CERT_VerifyCertificate(CERT_GetDefaultCertDB(),
+! cert, PR_FALSE,
+! (SECCertificateUsage)0,
+! timeboundary , NULL, NULL, NULL);
+! if (status == SECSuccess) {
+! break;
+! } /*
}
! if (status == SECSuccess) {