Log malformed hostnames in socks5 request respecting SafeLogging

diff --git a/changes/malformed-hostname-safe-logging b/changes/malformed-hostname-safe-logging
new file mode 100644 (file)
index 0000000..9300726
--- /dev/null
+++ b/changes/malformed-hostname-safe-logging
@@ -0,0 +1,3 @@
+  o Minor bugfixes:
+    - When logging malformed hostnames in socks5 requests, respect
+      SafeLogging configuration

diff --git a/src/or/buffers.c b/src/or/buffers.c
index 2d7dd937d8ff0e994ceb8a6714e38e7228b0421d..85fcbc64e8b5b32d9e4ca08e6d34a4abeb255ef1 100644 (file)
--- a/src/or/buffers.c
+++ b/src/or/buffers.c
@@ -1842,7 +1842,7 @@ parse_socks(const char *data, size_t datalen, socks_request_t *req,
             log_warn(LD_PROTOCOL,
                      "Your application (using socks5 to port %d) gave Tor "
                      "a malformed hostname: %s. Rejecting the connection.",
-                     req->port, escaped(req->address));
+                     req->port, escaped_safe_str_client(req->address));
             return -1;
           }
           if (log_sockstype)