diff options
| -rw-r--r-- | NEWS | 1 | ||||
| -rw-r--r-- | doc/TODO | 2 | ||||
| -rw-r--r-- | doc/tex/examples.tex | 2 |
3 files changed, 5 insertions, 0 deletions
@@ -7,6 +7,7 @@ Version 1.1.12 - Added some default limits in the verification of certificate chains, to avoid denial of service attacks. Also added gnutls_certificate_set_verify_limits() to override them. +- Added gnutls_certificate_verify_peers2(). Version 1.1.11 (16/07/2004) - Added the '_t' suffix to all exported symbols. @@ -12,6 +12,8 @@ Current list: * Enforce the constraints for verify_peers() or similar, to openpgp verification functions as well. This needs to be checked a bit. * Verify added CRLs +* Add functions to import certificates, private keys, etc. from + files similar to gnutls_x509_crt_import(). * Document the format for the supported DN attributes. * Add support for Certificate Extensions Profile for Qualified Certificates (rfc3039) diff --git a/doc/tex/examples.tex b/doc/tex/examples.tex index 3c1152e00e..0b1fccaba5 100644 --- a/doc/tex/examples.tex +++ b/doc/tex/examples.tex @@ -31,6 +31,8 @@ verified. That is, you have to verify the signature in peer's certificate, the hostname in the certificate, and expiration dates. Just after this step you should treat the connection as being a secure one. The following function is an example on how to verify the peer's certificate chain. +This is an advanced case. Things in a TLS session may be simplified by using +\printfunc{gnutls_certificate_verify_peers2}{gnutls\_certificate\_verify\_peers2}. \input{ex-verify} |