Browse Source

Log malformed hostnames in socks5 request respecting SafeLogging

Andreas Stieger 8 years ago
parent
commit
19df037e53
2 changed files with 4 additions and 1 deletions
  1. 3 0
      changes/malformed-hostname-safe-logging
  2. 1 1
      src/or/buffers.c

+ 3 - 0
changes/malformed-hostname-safe-logging

@@ -0,0 +1,3 @@
+  o Minor bugfixes:
+    - When logging malformed hostnames in socks5 requests, respect
+      SafeLogging configuration

+ 1 - 1
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)