From 5459d4154060b366afd203d7445823c34f82b83a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?G=C3=BCnter=20Obiltschnig?= Date: Fri, 10 Oct 2014 10:14:53 +0200 Subject: [PATCH] updated README --- NetSSL_Win/doc/README.txt | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/NetSSL_Win/doc/README.txt b/NetSSL_Win/doc/README.txt index 4d38a45fa..ef3152e76 100644 --- a/NetSSL_Win/doc/README.txt +++ b/NetSSL_Win/doc/README.txt @@ -19,9 +19,8 @@ These are discussed below: Please refer to the header file documentation for more information. Furthermore, the following Context methods are not available in NetSSL_Win: addChainCertificate(), disableStatelessSessionResumption(), - enableExtendedCertificateVerification(), enableSessionCache(), - extendedCertificateVerificationEnabled(), flushSessionCache(), - getSessionCacheSize(), getSessionTimeout(), sessionCacheEnabled(), + enableSessionCache(),flushSessionCache(), + getSessionCacheSize(), getSessionTimeout(), setSessionCacheSize(), setSessionTimeout(), sslContext(), useCertificate(), usePrivateKey(). @@ -37,7 +36,7 @@ Certificate and Certificate Stores ---------------------------------- The test suite and samples expect a certificate/private key file named -any.pem, located in the current working directory. This can be changed +any.pfx, located in the current working directory. This can be changed by editing the testrunner.xml/TestSuite.xml configuration files. Alternatively, a certificate from the Windows certificate store can be used. A suitable self-signed certificate can be created using the Windows