Package: privoxy Version: 3.0.3-2-1 Severity: wishlist When using Privoxy with Tor, accidentally omitting the last parameter to the forward-socks4a line in the /etc/privoxy/config causes Privoxy to simply ignore it and pass requests on out to the Net unencrypted and in a non-onion-routed fashion. This creates an extra opportunity for user error where there need not be one. Ideally, Privoxy should fail to start if the configuration file is ambiguous or malformed in any way.
---> Drake Wilson -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.16.19-ampersand Locale: LANG=C, LC_CTYPE=C Versions of packages privoxy depends on: ii adduser 3.56 Add and remove users and groups ii libc6 2.3.6-7 GNU C Library: Shared libraries ii libpcre3 6.4-1.0.1 Perl 5 Compatible Regular Expressi ii logrotate 3.7-2 Log rotation utility -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
