[Privoxy-commits] [privoxy] 02/02: wolfSSL: Use LIBWOLFSSL_VERSION_HEX to decide whether or not to use WOLFSSL_X509_V_OK

User Git git at git.privoxy.org
Mon Apr 1 17:21:51 CEST 2024


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

git pushed a commit to branch master
in repository privoxy.

commit b0a88373c964ed31e953edc68b75d657b85c3e69
Author: Fabian Keil <fk at fabiankeil.de>
AuthorDate: Mon Apr 1 17:19:06 2024 +0200

    wolfSSL: Use LIBWOLFSSL_VERSION_HEX to decide whether or not to use WOLFSSL_X509_V_OK
    
    As Roland pointed out, in older wolfSSL releases X509_V_OK
    is an enum so the previous commit 838bc3c0e did not work
    as expected there.
---
 wolfssl.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/wolfssl.c b/wolfssl.c
index 10ecd6b0..7f6c9646 100644
--- a/wolfssl.c
+++ b/wolfssl.c
@@ -1201,10 +1201,10 @@ extern int create_server_ssl_connection(struct client_state *csp)
    {
       long verify_result = wolfSSL_get_error(ssl, connect_ret);
 
-#ifdef X509_V_OK
-      if (verify_result == X509_V_OK)
-#else
+#if LIBWOLFSSL_VERSION_HEX > 0x05005004
       if (verify_result == WOLFSSL_X509_V_OK)
+#else
+      if (verify_result == X509_V_OK)
 #endif
       {
          ret = 0;

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.


More information about the Privoxy-commits mailing list