diff options
Diffstat (limited to 'docs/api/chapters')
| -rw-r--r-- | docs/api/chapters/compiling-and-linking.sgml | 2 | ||||
| -rw-r--r-- | docs/api/chapters/init-and-shutdown.sgml | 2 | ||||
| -rw-r--r-- | docs/api/chapters/new-crypto.sgml | 6 | ||||
| -rw-r--r-- | docs/api/chapters/sign-and-encrypt.sgml | 2 | ||||
| -rw-r--r-- | docs/api/chapters/using-contexts.sgml | 4 | ||||
| -rw-r--r-- | docs/api/chapters/verify-and-decrypt.sgml | 2 |
6 files changed, 9 insertions, 9 deletions
diff --git a/docs/api/chapters/compiling-and-linking.sgml b/docs/api/chapters/compiling-and-linking.sgml index 2cc6e44d..f184c6a4 100644 --- a/docs/api/chapters/compiling-and-linking.sgml +++ b/docs/api/chapters/compiling-and-linking.sgml @@ -161,7 +161,7 @@ clean: <listitem><para>xmlsec1-config script <example> <title>Using xmlsec1-config script in a Makefile - to select crypto engine (gnutls) at linking time.</title> + to select crypto engine (e.g. gnutls) at linking time.</title> <programlisting><![CDATA[ PROGRAM = test PROGRAM_FILES = test.c diff --git a/docs/api/chapters/init-and-shutdown.sgml b/docs/api/chapters/init-and-shutdown.sgml index 4cf869f7..688a6372 100644 --- a/docs/api/chapters/init-and-shutdown.sgml +++ b/docs/api/chapters/init-and-shutdown.sgml @@ -6,7 +6,7 @@ <itemizedlist> <listitem><para>libxml library;</para></listitem> <listitem><para>libxslt library;</para></listitem> - <listitem><para>crypto library (OpenSSL, GnuTLS, NSS, ...);</para></listitem> + <listitem><para>crypto library (OpenSSL, GnuTLS, GCrypt, NSS, ...);</para></listitem> <listitem><para>xmlsec library (<link linkend="xmlSecInit">xmlSecInit</link> and <link linkend="xmlSecShutdown">xmlSecShutdown</link> diff --git a/docs/api/chapters/new-crypto.sgml b/docs/api/chapters/new-crypto.sgml index 08a936e5..52191417 100644 --- a/docs/api/chapters/new-crypto.sgml +++ b/docs/api/chapters/new-crypto.sgml @@ -4,7 +4,7 @@ <title>Overview.</title> <para>XML Security Library can support practicaly any cryptographic library. Currently, it has "out-of-the-box" support for OpenSSL, - NSS and GnuTLS. If your favorite library is not supported yet then + MSCrypto, NSS, GnuTLS and GCrypt. If your favorite library is not supported yet then you can write necessary code yourself. If you and your company (university, ...) are willing to share the results of your work I would be happy to add support for new libraries to the main XML Security @@ -14,7 +14,7 @@ <link linkend="xmlsec-notes-structure">separates</link> the cryptographic library (engine) specific code in an "xmlsec-<crypto>" library (where "<crypto>" is - "openssl", "gnutls", "nss", etc.) which includes following items: + "openssl", "mscrypt", "gnutls", "gcrypt", "nss", etc.) which includes following items: <itemizedlist> <listitem><para> xmlSecCryptoApp* functions. @@ -186,7 +186,7 @@ src/mycrypto/Makefile <example> <title>Compiling the results.</title> <programlisting><![CDATA[ -./autogen.sh --without-openssl --without-nss --without-gnutls \ +./autogen.sh --without-openssl --without-nss --without-gnutls --without-gcrypt \ --with-mycrypto=$HOME --disable-tmpl-tests make ]]></programlisting> diff --git a/docs/api/chapters/sign-and-encrypt.sgml b/docs/api/chapters/sign-and-encrypt.sgml index 58ff04ac..72b969b6 100644 --- a/docs/api/chapters/sign-and-encrypt.sgml +++ b/docs/api/chapters/sign-and-encrypt.sgml @@ -20,7 +20,7 @@ <sect1 id="xmlsec-notes-sign" > <title>Signing a document.</title> - <para>The typical siganture process includes following steps: + <para>The typical signature process includes following steps: <itemizedlist> <listitem><para> Prepare data for signature. diff --git a/docs/api/chapters/using-contexts.sgml b/docs/api/chapters/using-contexts.sgml index 0dc1c263..48a336d9 100644 --- a/docs/api/chapters/using-contexts.sgml +++ b/docs/api/chapters/using-contexts.sgml @@ -71,13 +71,13 @@ verify_file(xmlSecKeysMngrPtr mngr, const char* xml_file) { /* limit the Reference URI attributes to empty or NULL */ dsigCtx->enabledReferenceUris = xmlSecTransformUriTypeEmpty; - /* limit allowed transforms for siganture and reference processing */ + /* limit allowed transforms for signature and reference processing */ if((xmlSecDSigCtxEnableSignatureTransform(dsigCtx, xmlSecTransformInclC14NId) < 0) || (xmlSecDSigCtxEnableSignatureTransform(dsigCtx, xmlSecTransformExclC14NId) < 0) || (xmlSecDSigCtxEnableSignatureTransform(dsigCtx, xmlSecTransformSha1Id) < 0) || (xmlSecDSigCtxEnableSignatureTransform(dsigCtx, xmlSecTransformRsaSha1Id) < 0)) { - fprintf(stderr,"Error: failed to limit allowed siganture transforms\n"); + fprintf(stderr,"Error: failed to limit allowed signature transforms\n"); goto done; } if((xmlSecDSigCtxEnableReferenceTransform(dsigCtx, xmlSecTransformInclC14NId) < 0) || diff --git a/docs/api/chapters/verify-and-decrypt.sgml b/docs/api/chapters/verify-and-decrypt.sgml index 699d19b6..382c97c1 100644 --- a/docs/api/chapters/verify-and-decrypt.sgml +++ b/docs/api/chapters/verify-and-decrypt.sgml @@ -20,7 +20,7 @@ <sect1 id="xmlsec-notes-verify" > <title>Verifying a signed document</title> - <para>The typical siganture verification process includes following steps: + <para>The typical signature verification process includes following steps: <itemizedlist> <listitem><para> Load keys, X509 certificates, etc. in the <link linkend="xmlSecKeysMngr">keys manager</link> . |