.\" Hal Burgiss <hal@foobox.net> \r
.\" for Junkbuster developers: ijbswa-developers@lists.sourceforge.net\r
.\"\r
-.TH JUNKBUSTER 1 "v2.9.9 (alpha) Date: 2001/10/14"\r
+.TH JUNKBUSTER 1 "v2.9.11 (beta) Date: 2002/02/24"\r
\r
.SH NAME\r
\fBjunkbuster\fP\r
\s-2(TM)\s+2\r
.SH SYNOPSIS\r
\fBjunkbuster\fP\r
-\fI\&[config_file] &\fP\r
+\fI\&[config_file]\fP\r
.br\r
\fBjunkbstr.exe\fP\r
\fI\&[config_file]\fP\r
.P\r
If the configuration file is not specified on the command line,\r
\fBJunkbuster\fP will look for a file named \fIconfig\fP in the \r
-current directory (except on Amiga where it will look for \r
-\fIAmiTCP:db/junkbuster/config\fP and Win32 where it will try \r
-\fIjunkbstr.txt\fP).\r
+current directory (except on Win32 where it will try \fIconfig.txt\fP).\r
\r
\r
.SH DESCRIPTION\r
\fB\&https:\fP\r
\s-2URL\s0s\r
won't be proxied.\r
+.P\r
+For other browser, check the documentation.\r
\r
.SH CONFIGURATION\r
-All \fBJunkbuster\fP configuration is done via the various configuarion \r
+All \fBJunkbuster\fP configuration is done via the various configuration \r
files. The default configuration files are: \fIconfig\fP, \r
-\fIactionsfile\fP, and \fIre_filterfile\fP. These are well commented. \r
+\fIijb.action\fP, and \fIre_filterfile\fP. These are well commented. \r
On Unix and Unix-like systems, these are located in \fI/etc/junkbuster/\fP \r
-by default. On Windows and OS/2, these files are in the same directory \r
+by default. On Windows, OS/2 and AmigaOS, these files are in the same directory \r
as the \fBJunkbuster\fP executable. \r
.P\r
The name and number of configuration files has changed from previous versions,\r
and is subject to change as development progresses. In fact, the configuration\r
itself is changed and much more sophisticated. See the user-manual for a brief\r
explanation of all configuration options.\r
+.P\r
+\fBJunkbuster's\fP configuration parameters can be viewed at\r
+\fIhttp://i.j.b/\fP. This is an internal page. In\r
+addition, the \fIijb.action\fP file can be edited here, and \fBJunkbuster\fP can\r
+be toggled on/off.\r
\r
.SH "SAMPLE CONFIGURATION"\r
.PP\r
-A brief example of what an \fIactionsfile\fP configuration might look like:\r
+A brief example of what an \fIijb.action\fP configuration might look like:\r
.PP\r
.nf\r
\r
# Define a few useful custom aliases for later use\r
{{alias}}\r
+# Don't accept cookies\r
+no-cookies = +no-cookies-set +no-cookies-read\r
+# Do accept cookies\r
-no-cookies = -no-cookies-set -no-cookies-read\r
+imageblock = +block +image\r
\r
-hide-user-agent \\\r
-image \\\r
+image-blocker{blank} \\\r
- +no-cookies-read \\\r
- +no-cookies-set \\\r
+ +no-cookies-keep \\\r
+ -no-cookies-read \\\r
+ -no-cookies-set \\\r
+no-popups \\\r
- +vanilla-wafer \\\r
+ -vanilla-wafer \\\r
+ -wafer \\\r
}\r
/\r
\r
# Now set exceptions to the above defined policies #######\r
\r
-# Sites that DO need cookies\r
-{-no-cookies}\r
+# Sites where we want persistant cookies\r
+{-no-cookies -no-cookies-keep}\r
.redhat.com\r
.sun.com\r
.yahoo.com\r
.msdn.microsoft.com\r
\r
# This site requires cookies AND 'fast-redirects' on\r
-{-no-cookies -fast-redirects}\r
+{-no-cookies -no-cookies-keep -fast-redirects}\r
.nytimes.com\r
\r
# Add custom headers, and turn off filtering of page source\r
+add-header{X-User-Tracking: No thanks!} -filter}\r
privacy.net\r
\r
+# Block, and treat these URLs as 'images'.\r
{+imageblock}\r
.adforce.imgis.com\r
.ad.preferences.com/image.*\r
.br\r
\fI/etc/junkbuster/config\fP\r
.br\r
-\fI/etc/junkbuster/actionsfile\fP\r
+\fI/etc/junkbuster/ijb.action\fP\r
+.br\r
+\fI/etc/junkbuster/ijb-advanced.action\fP\r
+.br\r
+\fI/etc/junkbuster/ijb-basic.action\fP\r
+.br\r
+\fI/etc/junkbuster/ijb-intermediate.action\fP\r
.br\r
\fI/etc/junkbuster/re_filterfile\fP\r
.br\r
+\fI/etc/junkbuster/trust\fP\r
+.br\r
+\fI/etc/junkbuster/templates/*\fP\r
+.br\r
\fI/var/log/junkbuster/logfile\fP\r
\r
.P\r
and build configuration. More documentation should be included in the local\r
documentation directory, though is not complete at this time.\r
\r
+.SH SIGNALS\r
+\fBJunkbuster\fP use the signal \fISIGHUP\fP (see kill -l) to reload all configuration\r
+files (see CONFIGURATION). This includes the re-open of the logfiles\r
+(logfile and jarfile) eg. used\r
+after rotation of the logfiles by logrotate.\r
+The \fISIGHUP\fP behavior is only for UNIX like OS'.\r
+.br\r
+However the configfile will be re-read if \fBJunkbuster\fP detects a changed\r
+modification time and then behaves like a re-start of \fBJunkbuster\fP \r
+in context of all the pertinent files.\r
+ \r
.SH NOTES\r
This is a development version of \fBJunkbuster\fP. Not all features are \r
complete.\r
how and where to report bugs.\r
\r
.SH SEE ALSO\r
+.br\r
+http://i.j.b/\r
+.br\r
http://ijbswa.sourceforge.net/\r
.br\r
http://sourceforge.net/projects/ijbswa\r
.br\r
http://www.junkbusters.com/ht/en/cookies.html\" cookies.html#\r
.br\r
-http://ijbswa.sourceforge.net/config/\r
-.br\r
http://privacy.net/analyze/\r
.br\r
http://www.squid-cache.org/\r
+.br\r
+http://linuxalpha.ch/packages/\r
\r
.SH DEVELOPMENT TEAM\r
.br\r
.br\r
Haroon Rafique\r
.br\r
- Jorg Strohmayer\r
+ Joerg Strohmayer\r
.br\r
Shamim Mohamed\r
.br\r
projects / privoxy.git / blobdiff