privoxy.1 8.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240
  1. .\" This manpage has been generated by docbook2man-spec.pl
  2. .\" (included in the Privoxy source tarball) from a DocBook document.
  3. .TH "PRIVOXY" "1" "22 July 2020" "Privoxy 3.0.29 UNRELEASED" ""
  4. .SH NAME
  5. privoxy \- Privacy Enhancing Proxy
  6. .SH SYNOPSIS
  7. \fBprivoxy\fR [\fB\-\-chroot\fR ] [\fB\-\-config-test\fR ] [\fB\-\-help\fR ] [\fB\-\-no-daemon\fR ] [\fB\-\-pidfile \fIpidfile\fB\fR ] [\fB\-\-pre-chroot-nslookup \fIhostname\fB\fR ] [\fB\-\-user \fIuser[.group]\fB\fR ] [\fB\-\-version\fR ] [\fB\fIconfigfile\fB\fR ]
  8. .SH "OPTIONS"
  9. .PP
  10. \fBPrivoxy\fR may be invoked with the following command line
  11. options:
  12. .TP
  13. \fB\-\-chroot\fR
  14. Before changing to the user ID given in the \-\-user option, chroot to
  15. that user's home directory, i.e. make the kernel pretend to the
  16. \fBPrivoxy\fR process that the directory tree starts
  17. there. If set up carefully, this can limit the impact of possible
  18. vulnerabilities in \fBPrivoxy\fR to the files contained in
  19. that hierarchy.
  20. .TP
  21. \fB\-\-config-test\fR
  22. Exit after loading the configuration files before binding to
  23. the listen address. The exit code signals whether or not the
  24. configuration files have been successfully loaded.
  25. If the exit code is 1, at least one of the configuration files
  26. is invalid, if it is 0, all the configuration files have been
  27. successfully loaded (but may still contain errors that can
  28. currently only be detected at run time).
  29. This option doesn't affect the log setting, combination with
  30. "--no-daemon" is recommended if a configured log file shouldn't
  31. be used.
  32. .TP
  33. \fB\-\-help\fR
  34. Print brief usage info and exit.
  35. .TP
  36. \fB\-\-no-daemon\fR
  37. Don't become a daemon, i.e. don't fork and become process group
  38. leader, don't detach from controlling tty, and do all logging there.
  39. .TP
  40. \fB\-\-pidfile \fIpidfile\fB\fR
  41. On startup, write the process ID to \fIpidfile\fR.
  42. Delete the \fIpidfile\fR on exit.
  43. Failure to create or delete the \fIpidfile\fR
  44. is non-fatal. If no \fB\-\-pidfile\fR option is given, no PID file will be used.
  45. .TP
  46. \fB\-\-pre-chroot-nslookup \fIhostname\fB\fR
  47. Initialize the resolver library using \fIhostname\fR
  48. before chroot'ing. On some systems this reduces the number of files
  49. that must be copied into the chroot tree.
  50. .TP
  51. \fB\-\-user \fIuser[.group]\fB\fR
  52. After (optionally) writing the PID file, assume the user ID of
  53. \fIuser\fR and the GID of
  54. \fIgroup\fR, or, if the optional
  55. \fIgroup\fR was not given, the default group of
  56. \fIuser\fR. Exit if the privileges are not
  57. sufficient to do so.
  58. .TP
  59. \fB\-\-version\fR
  60. Print version info and exit.
  61. .PP
  62. If the \fIconfigfile\fR is not specified on the command line,
  63. \fBPrivoxy\fR will look for a file named
  64. \fIconfig\fR in the current directory. If no
  65. \fIconfigfile\fR is found, \fBPrivoxy\fR will
  66. fail to start.
  67. .SH "DESCRIPTION"
  68. .PP
  69. Privoxy is a non-caching web proxy with advanced filtering capabilities
  70. for enhancing privacy, modifying web page data and HTTP headers, controlling
  71. access, and removing ads and other obnoxious Internet junk. Privoxy has a
  72. flexible configuration and can be customized to suit individual needs and tastes.
  73. It has application for both stand-alone systems and multi-user networks.
  74. .PP
  75. Privoxy is Free Software and licensed under the GNU GPLv2 or later.
  76. .PP
  77. Privoxy is an associated project of Software in the Public Interest (SPI).
  78. .PP
  79. Helping hands and donations are welcome:
  80. .PP
  81. .TP 0.2i
  82. \(bu
  83. https://www.privoxy.org/faq/general.html#PARTICIPATE
  84. .TP 0.2i
  85. \(bu
  86. https://www.privoxy.org/faq/general.html#DONATE
  87. .SH "INSTALLATION AND USAGE"
  88. .PP
  89. Browsers can either be individually configured to use
  90. \fBPrivoxy\fR as a HTTP proxy (recommended),
  91. or \fBPrivoxy\fR can be combined with a packet
  92. filter to build an intercepting proxy
  93. (see \fIconfig\fR). The default setting is for
  94. localhost, on port 8118 (configurable in the main config file). To set the
  95. HTTP proxy in Firefox, go through: \fBTools\fR;
  96. \fBOptions\fR; \fBGeneral\fR;
  97. \fBConnection Settings\fR;
  98. \fBManual Proxy Configuration\fR.
  99. .PP
  100. For Internet Explorer, go through: \fBTools\fR;
  101. \fBInternet Properties\fR; \fBConnections\fR;
  102. \fBLAN Settings\fR.
  103. .PP
  104. The Secure (SSL) Proxy should also be set to the same values, otherwise
  105. https: URLs will not be proxied. Note: \fBPrivoxy\fR can only
  106. proxy HTTP and HTTPS traffic. Do not try it with FTP or other protocols.
  107. HTTPS presents some limitations, and not all features will work with HTTPS
  108. connections.
  109. .PP
  110. For other browsers, check the documentation.
  111. .SH "CONFIGURATION"
  112. .PP
  113. \fBPrivoxy\fR can be configured with the various configuration
  114. files. The default configuration files are: \fIconfig\fR,
  115. \fIdefault.filter\fR, \fIdefault.action\fR and
  116. \fIdefault.action\fR. \fIuser.action\fR should
  117. be used for locally defined exceptions to the default rules in
  118. \fImatch-all.action\fR and \fIdefault.action\fR,
  119. and \fIuser.filter\fR for locally defined filters. These are
  120. well commented. On Unix and Unix-like systems, these are located in
  121. \fI/etc/privoxy/\fR by default.
  122. .PP
  123. \fBPrivoxy\fR uses the concept of \fBactions\fR
  124. in order to manipulate the data stream between the browser and remote sites.
  125. There are various actions available with specific functions for such things
  126. as blocking web sites, managing cookies, etc. These actions can be invoked
  127. individually or combined, and used against individual URLs, or groups of URLs
  128. that can be defined using wildcards and regular expressions. The result is
  129. that the user has greatly enhanced control and freedom.
  130. .PP
  131. The actions list (ad blocks, etc) can also be configured with your
  132. web browser at http://config.privoxy.org/
  133. (assuming the configuration allows it).
  134. \fBPrivoxy's\fR configuration parameters can also be viewed at
  135. the same page. In addition, \fBPrivoxy\fR can be toggled on/off.
  136. This is an internal page, and does not require Internet access.
  137. .PP
  138. See the \fIUser Manual\fR for a detailed
  139. explanation of installation, general usage, all configuration options, new
  140. features and notes on upgrading.
  141. .SH "FILES"
  142. .nf
  143. \fI/usr/sbin/privoxy\fR
  144. \fI/etc/privoxy/config\fR
  145. \fI/etc/privoxy/match-all.action\fR
  146. \fI/etc/privoxy/default.action\fR
  147. \fI/etc/privoxy/user.action\fR
  148. \fI/etc/privoxy/default.filter\fR
  149. \fI/etc/privoxy/user.filter\fR
  150. \fI/etc/privoxy/trust\fR
  151. \fI/etc/privoxy/templates/*\fR
  152. \fI/var/log/privoxy/logfile\fR
  153. .fi
  154. .PP
  155. Various other files should be included, but may vary depending on platform
  156. and build configuration. Additional documentation should be included in the local
  157. documentation directory.
  158. .SH "SIGNALS"
  159. .PP
  160. \fBPrivoxy\fR terminates on the \fBSIGINT\fR
  161. and \fBSIGTERM\fR signals. Log
  162. rotation scripts may cause a re-opening of the logfile by sending a
  163. \fBSIGHUP\fR to \fBPrivoxy\fR. Note that unlike
  164. other daemons, \fBPrivoxy\fR does not need to be made aware of
  165. config file changes by \fBSIGHUP\fR -- it will detect them
  166. automatically. Signals other than the ones listed above aren't explicitly
  167. handled and result in the default action defined by the operating system.
  168. .SH "NOTES"
  169. .PP
  170. This is a UNRELEASED version of \fBPrivoxy\fR. Not
  171. all features are well tested.
  172. .PP
  173. Please see the \fIUser Manual\fR on how to contact the
  174. developers, for feature requests, reporting problems, and other questions.
  175. .SH "SEE ALSO"
  176. .PP
  177. Other references and sites of interest to \fBPrivoxy\fR
  178. users:
  179. https://www.privoxy.org/,
  180. the \fBPrivoxy\fR Home page.
  181. https://www.privoxy.org/faq/,
  182. the \fBPrivoxy\fR FAQ.
  183. https://www.privoxy.org/developer-manual/,
  184. the \fBPrivoxy\fR developer manual.
  185. https://sourceforge.net/projects/ijbswa/,
  186. the Project Page for \fBPrivoxy\fR on
  187. SourceForge.
  188. http://config.privoxy.org/,
  189. the web-based user interface. \fBPrivoxy\fR must be
  190. running for this to work. Shortcut: http://p.p/
  191. https://sourceforge.net/tracker/?group_id=11118&atid=460288, to submit ``misses'' and other
  192. configuration related suggestions to the developers.
  193. .SH "DEVELOPMENT TEAM"
  194. .nf
  195. Fabian Keil, lead developer
  196. David Schmidt
  197. Lee Rian
  198. Roland Rosenfeld
  199. Ian Silvester
  200. .fi
  201. .SH "COPYRIGHT AND LICENSE"
  202. .SS "COPYRIGHT"
  203. .PP
  204. Copyright (C) 2001-2020 by Privoxy Developers <privoxy-devel@lists.privoxy.org>
  205. .PP
  206. Some source code is based on code Copyright (C) 1997 by Anonymous Coders
  207. and Junkbusters, Inc. and licensed under the \fIGNU General Public
  208. License\fR.
  209. .SS "LICENSE"
  210. .PP
  211. \fBPrivoxy\fR is free software; you can
  212. redistribute and/or modify its source code under the terms
  213. of the \fIGNU General Public License\fR
  214. as published by the Free Software Foundation, either version 2
  215. of the license, or (at your option) any later version.
  216. .PP
  217. The same is true for \fBPrivoxy\fR binaries
  218. unless they are linked with
  219. mbed TLS in which
  220. case you can redistribute them and/or modify them under the terms
  221. of the \fIGNU General Public License\fR
  222. as published by the Free Software Foundation, either version 3
  223. of the license, or (at your option) any later version.
  224. .PP
  225. \fBPrivoxy\fR is distributed in the hope that
  226. it will be useful, but WITHOUT ANY WARRANTY; without even the implied
  227. warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
  228. See the \fIlicense\fR for details.