gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-SVN] [gnurl] 41/219: README: Schannel, stop calling it "winssl"


From: gnunet
Subject: [GNUnet-SVN] [gnurl] 41/219: README: Schannel, stop calling it "winssl"
Date: Wed, 22 May 2019 19:16:20 +0200

This is an automated email from the git hooks/post-receive script.

ng0 pushed a commit to branch master
in repository gnurl.

commit 37c43bf70c43ae02d36a774e511dc9fa20f64980
Author: Steve Holme <address@hidden>
AuthorDate: Tue Apr 9 20:34:10 2019 +0100

    README: Schannel, stop calling it "winssl"
    
    Stick to "Schannel" everywhere - follow up to 180501cb.
---
 projects/README | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/projects/README b/projects/README
index be3e1e0e3..62b998656 100644
--- a/projects/README
+++ b/projects/README
@@ -151,9 +151,9 @@ Notes
 Legacy Windows and SSL
 ======================
 
-   Some of the project configurations allow the use of WinSSL (specifically
-   Schannel from Windows SSPI), the native SSL library in Windows. However,
-   WinSSL in Windows <= XP is unable to connect to servers that no longer
-   support the legacy handshakes and algorithms used by those versions. If
-   you will be using curl in one of those earlier versions of Windows you
-   should choose another SSL backend such as OpenSSL.
+   Some of the project configurations allow the use of Schannel, the native
+   SSL library in Windows which forms part of Windows SSPI. However, Schannel
+   in Windows <= XP is unable to connect to servers that no longer support the
+   legacy handshakes and algorithms used by those versions. If you will be
+   using curl in one of those earlier versions of Windows you should choose
+   another SSL backend such as OpenSSL.

-- 
To stop receiving notification emails like this one, please contact
address@hidden



reply via email to

[Prev in Thread] Current Thread [Next in Thread]