Your message dated Mon, 22 Aug 2016 14:23:40 +0200
with message-id <[email protected]>
and subject line Re: Bug#316203: privoxy: toggle the use of tor / direct 
connection
has caused the Debian Bug report #316203,
regarding privoxy: toggle the use of tor / direct connection
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
316203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316203
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: privoxy
Version: 3.0.3-3
Severity: wishlist

I'd love to be able to toggle privoxy's use of TOR (via socks) vs.
direct internet connection as easily as toggling the filtering of
privoxy.

Rationale: I'm very fond of privoxy's filtering capabilities, and would
like to use them all the time. In addition, I have to use TOR from time
to time in order to access certain web pages. Unfortunately, TOR
considerably slows down web browsing (at least from my location), so
that its permanent use is not enjoyable at present.

While privoxy's filtering can be switched on and off very easily (and
quickly, e.g. using a browser shortcut), this is not the case for its
forwarding. Changing the browser's proxy settings is also not exactly
quick to do (and would leave me without privoxy's service).

Thus, I'd very much like a function to toggle between various
"forwarding"-states in the same fashion that filtering can be toggled.

Do you think this is a reasonable feature request? Shouldn't it be
relatively easy to implement?

Florian

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-1-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages privoxy depends on:
ii  adduser                     3.63         Add and remove users and groups
ii  libc6                       2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  libpcre3                    5.0-1.1      Perl 5 Compatible Regular Expressi
ii  logrotate                   3.7-5        Log rotation utility

-- no debconf information

-- 
  __     
 / _|___
| |_/ __|       Florian Schlichting         __O
|  _\__ \       +86 (0)10 84070216 h      _-\<,_
|_| |___/       +86 (0)13521877533 m     (_)/ (_)
       

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
Source: privoxy
Source-Version: 3.0.25-1

On Wed, 29 Jun 2005, Florian Schlichting wrote:

> I'd love to be able to toggle privoxy's use of TOR (via socks) vs.
> direct internet connection as easily as toggling the filtering of
> privoxy.

Good news: this is now possible by using the new client-tag feature,
which was implemented in privoxy 3.0.25.

For this you have to define a tag in /etc/privoxy/config like this:

client-specific-tag tor Use TOR Proxy

Then you have to define an action in (for example)
/etc/privoxy/user.action like this:

{+forward-override{forward-socks5t 127.0.0.1:9050 .} }
CLIENT-TAG:^tor$

This changes forwarding towards the tor proxy, if client tag "tor" is
active.

Now you can enable/disable this tag in the browser via
http://config.privoxy.org/client-tags


This all may be optimized by adding stricter cookie policy etc. if
client-tag tor is active.

You also may think about defining tor as the default forward proxy and
define a client tag "no-tor", the (temporarily) disabled tor, since
restarting privoxy disables all former active client-tags and you have
to manually enable them.  So restarting privoxy with my above example,
may disable tor without your notice...

I think that this solves your issue, so I close it now.

Tschoeeee

        Roland

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to