From 53e2493ea524e3afbb0a7b733a0d18765ca432b0 Mon Sep 17 00:00:00 2001
From: Daniel Stenberg <daniel@haxx.se>
Date: Mon, 18 Jan 2021 16:40:39 +0100
Subject: libssh: avoid plain free() of libssh-memory

Since curl's own memory debugging system redefines free() calls to track
and fiddle with memory, it cannot be used on memory allocated by 3rd
party libraries.

Third party libraries SHOULD NOT require free() to release allocated
resources for this reason - and libs can use separate healp allocators
on some systems (like Windows) so free() doesn't necessarily work
anyway.

Filed as an issue with libssh: https://bugs.libssh.org/T268
---
 lib/vssh/libssh.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'lib/vssh')

diff --git a/lib/vssh/libssh.c b/lib/vssh/libssh.c
index 70e0ded5e..3b630bcfa 100644
--- a/lib/vssh/libssh.c
+++ b/lib/vssh/libssh.c
@@ -532,10 +532,10 @@ static int myssh_is_known(struct connectdata *conn)
 
 cleanup:
   if(found_base64) {
-    free(found_base64);
+    (free)(found_base64);
   }
   if(known_base64) {
-    free(known_base64);
+    (free)(known_base64);
   }
   if(hash)
     ssh_clean_pubkey_hash(&hash);
-- 
cgit v1.2.1