From: Fabian Keil Date: Thu, 17 Jan 2013 14:29:45 +0000 (+0000) Subject: Shorten the description of the incorrect assertion in case of socks5 connection failures X-Git-Tag: v_3_0_20~28 X-Git-Url: http://www.privoxy.org/gitweb/show-status?a=commitdiff_plain;h=b61fe39c9ab8a0704add09cb5b97b94ed6509a13;p=privoxy.git Shorten the description of the incorrect assertion in case of socks5 connection failures --- diff --git a/ChangeLog b/ChangeLog index e296629d..0e932215 100644 --- a/ChangeLog +++ b/ChangeLog @@ -18,12 +18,8 @@ ChangeLog for Privoxy unresponsive after toggling it on or off through the taskbar icon. Reported by Tim H. in #3525694. - Fix the compilation on Windows when configured without IPv6 support. - - In socks5_connect(), do not try to print a negative number of socks - response bytes if the read() for the socks5 negotiation failed - completely. It's an API violation and can trigger an assert() in debug - builds with "debug 2" enabled. Except for the assert(), log_error() - already handled negative %N values gracefully so this commit only makes a - difference for debug builds. + - Fix an assertion that could cause debug builds to abort() in case of + socks5 connection failures with "debug 2" enabled. - Fix an assertion that could cause debug builds to abort() if a filter contained nul bytes in the replacement text. - Reject URLs with invalid port. Previously they were parsed incorrectly and