[PATCH 0/1] MR5690: secur32: Allow overriding GnuTLS debug level.

[PATCH 1/1] secur32: Allow overriding GnuTLS debug level.

[Daniel Lehman]

From: Daniel Lehman

---
 dlls/secur32/schannel_gnutls.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/dlls/secur32/schannel_gnutls.c b/dlls/secur32/schannel_gnutls.c
index fc16ded7a64..1af0682b269 100644
--- a/dlls/secur32/schannel_gnutls.c
+++ b/dlls/secur32/schannel_gnutls.c
@@ -1576,7 +1576,9 @@ static NTSTATUS process_attach( void *args )

if (TRACE_ON(secur32))
     {
-        pgnutls_global_set_log_level(4);
+        char *env = getenv("GNUTLS_DEBUG_LEVEL");
+        int level = env ? atoi(env) : 4;
+        pgnutls_global_set_log_level(level);
         pgnutls_global_set_log_function(gnutls_log);
     }

[PATCH 0/3] MR5690: secur32: Allow overriding GnuTLS debug level.

[Hans Leidekker (＠hans)]

bcrypt and crypt32 also use GnutTLS and set the log level to 4. If either of these dlls is loaded after secur32, setting GNUTLS_DEBUG_LEVEL to anything else will not take effect. We probably want to apply the same patch to bcrypt and crypt32 to avoid confusion.