summaryrefslogtreecommitdiff
path: root/libxmlsec
diff options
context:
space:
mode:
authorTor Lillqvist <tml@iki.fi>2013-05-15 10:42:04 +0300
committerTor Lillqvist <tml@iki.fi>2013-05-15 11:14:28 +0300
commitcb6d67c21f11811c5bc023b9565c1c1b1f4081fa (patch)
treeff8a4b192a2ca846d32111732563432244135910 /libxmlsec
parent1a357b7394ac7b48b72821bff1aae4706265d7a4 (diff)
Spelling "separate" (etc) correctly is hard
Diffstat (limited to 'libxmlsec')
-rw-r--r--libxmlsec/xmlsec1-noverify.patch4
1 files changed, 2 insertions, 2 deletions
diff --git a/libxmlsec/xmlsec1-noverify.patch b/libxmlsec/xmlsec1-noverify.patch
index c51540caa2aa..d483cb85bbc7 100644
--- a/libxmlsec/xmlsec1-noverify.patch
+++ b/libxmlsec/xmlsec1-noverify.patch
@@ -8,7 +8,7 @@
- return(cert);
- }
+ /* JL: OpenOffice.org implements its own certificate verification routine.
-+ The goal is to seperate validation of the signature
++ The goal is to separate 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 will not be
@@ -36,7 +36,7 @@
+
+ /*
+ JL: OpenOffice.org implements its own certificate verification routine.
-+ The goal is to seperate validation of the signature
++ The goal is to separate 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