How to start Privoxy after installation

I installed Privoxy in OpenSUSE 12.3, so I think it needs a command line to start or restart itself, just as the case in Fedora 18, how can I do?

Should be something like this:

su -
systemctl enable privoxyd.service
systemctl start privoxyd.service

These are general solutions to your question, I do not know Privoxy.

When it is a user application, you just type


in a terminal emulator (console). May be options, etc. must be added, but then you should read the docuumentation.

If it is a system service, then there is a chance that it can be found in YaST > System > System Servicess (runlevel) and then you can switch it on there.

Simply typing “privoxy” in a console might work only if installed in or configured a PATH.

If that doesn’t work, you need to find the executable by looking at the package file contents by either using YAST or the rpm command

rpm -ql *packagename*

Else, as always read the MAN pages.


Thank you very much, but there are new problem after inputting the two lines in the konsole, and restar Vidalia, the TOR browser aren’t able to connect to TOR, the TOR button turn into grey, until I configured the proxy in the TOR button preference to manually. Now the TOR Browser is working, but I want to know why I have this kind of problem that I never had in Fedora 18.

Which means that you are looking for people that have aquaintance with Fedora 18. I quit.

No, not have to. I just want to run Tor bundle browser in default configuration, no matter Fedora or OpenSUSE

I do not know if any of this is relevant. From the latest 12.3 updates:

Patch: openSUSE-2013-242 Kind: security Version: 1   
privoxy was updated to 3.0.21 stable fo fix CVE-2013-2503 (bnc#809123)  
- changes in 3.0.21  
 * On POSIX-like platforms, network sockets with file descriptor   
    values above FD_SETSIZE are properly rejected. Previously they   
    could cause memory corruption in configurations that allowed  
    the limit to be reached.   
 * Proxy authentication headers are removed unless the new directive  
    enable-proxy-authentication-forwarding is used. Forwarding the  
   headers potentionally allows malicious sites to trick the user  
    into providing them with login information.  
    Reported by Chris John Riley.  
 * Compiles on OS/2 again now that unistd.h is only included   
    on platforms that have it.   
 * The show-status page shows the FEATURE_STRPTIME_SANITY_CHECKS status. 
 * A couple of assert()s that could theoretically dereference   
   NULL pointers in debug builds have been relocated.  
 * Added an LSB info block to the generic start script.  
    Based on a patch from Natxo Asenjo. 
 * The max-client-connections default has been changed to 128   
  which should be more than enough for most setups.  
 * Block rover.ebay./ar.*\&adtype= instead of "/.*\&adtype=" which  
    caused too man false positives.   
    Reported by u302320 in #360284, additional feedback from Adam Piggott.  
 * Unblock '' and '/.*ADVrider'.  
    Anonymously reported in #3603636.  
 * Stop blocking '/js/slider\.js'.   
    Reported by Adam Piggott in #3606635 and _lvm in #2791160.  
 * Added an iframes filter.   
 * The whole GPLv2 text is included in the user manual now,  
    so Privoxy can serve it itself and the user can read it   
   without having to wade through GPLv3 ads first.   
 * Properly numbered and underlined a couple of section titles  
    in the config that where previously overlooked due to a flaw  
    in the conversion script. Reported by Ralf Jungblut.   
 * Improved the support instruction to hopefully make it harder to  
    unintentionally provide insufficient information when requesting 
    support. Previously it wasn't obvious that the information we need  
    in bug reports is usually also required in support requests. 
 * Removed documentation about packages that haven't been provided  
    in years.   
 * Only log the test number when not running in verbose mode  
    The position of the test is rarely relevant and it previously   
- for full list of changes see ChangeLog file shipped together with  
  this package  
809123 (bugzilla): VUL-0: CVE-2013-2503: privoxy: proxy spoofing by malicious servers 
CVE-2013-2503 (cve):  

The Tor Browser Bundle does not require Privoxy or any other packages to be installed in openSUSE, it is completely self-contained… sort of like how a Java applet is distributed.

IMO if you’re running TOR there is no need for a local anonymization proxy, TOR is supposed to do that for you so Privoxy is not needed.


Just a FYI…

Just out of curiousity since I was interested in testing Privoxy on my new 12.3,

Looks like it runs just fine.

Although Privoxy is in /sbin so you can type it from anywhere to start, apparently it doesn’t automatically know that the config is in /etc/privoxy/

So, the simple solution is to simply launch privoxy from where the config file is

cd /etc/privoxy

From that point, you should be able to point your web browser to localhost and things should work.

But, as I noted I doubt there is any benefit if you’re running the TOR browser bundle because in that case you’re already using a highly modified version of FF which shouldn’t leak the information that Privoxy would do for you. Privoxy is something you’d possibly consider if you were using one of your regular web browsers.