1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
|
######################################################################
#
# File : trust
#
# Purpose : Trustfiles can be used to build "allowlists"
# (versus the usual "blocklists" techniques).
#
# Copyright : Written by and Copyright (C) 2001-2023 the
# Privoxy team. https://www.privoxy.org/
#
# Based on the Internet Junkbuster originally written
# by and Copyright (C) 1997 Anonymous Coders and
# Junkbusters Corporation. http://www.junkbusters.com
#
# We value your feedback. However, to provide you with the best support,
# please note:
#
# * Use the support forum to get help:
# https://sourceforge.net/p/ijbswa/support-requests/
# * Submit bugs only thru our bug forum:
# https://sourceforge.net/p/ijbswa/bugs/
# Make sure that the bug has not already been submitted. Please try
# to verify that it is a Privoxy bug, and not a browser or site
# bug first. If you are using your own custom configuration, please
# try the stock configs to see if the problem is a configuration
# related bug. And if not using the latest development snapshot,
# please try the latest one. Or even better, git sources.
# * Submit feature requests only thru our feature request tracker:
# https://sourceforge.net/p/ijbswa/feature-requests/
#
# For any other issues, feel free to use the mailing lists.
# Anyone interested in actively participating in development and related
# discussions can join the appropriate mailing list here:
# https://lists.privoxy.org/mailman/listinfo. Archives are available
# here too.
#
######################################################################
#
# Sample Trustfile for Privoxy
# For this file to have any effect, the line in the main config file beginning
# with "trustfile" must be uncommented, with the name of this file following the
# word "trustfile".
# Trustfiles are an experimental feature used for building "allowlists"
# of "trusted" sites (versus the usual "blocklists" technique). For more
# detail, see https://www.privoxy.org/user-manual/config.html#TRUSTFILE.
# List trusted domains here. The default is to block any URL that is NOT
# referenced. Access to trusted domains includes all paths within that
# domain.
# Preceding a domain with a '+' character will designate that domain
# as a "trusted referrer", meaning any requests whose HTTP "Referer" headers
# contain an URL from that domain will be allowed, and the previously untrusted
# host will be dynamically added to this file. Thus, this builds a "white-list"
# of hosts the user is allowed to visit.
# Note this means that the file will grow with use!
# Also note that you can only trust referrers if you control the user's
# system and make sure that there are no programs available that allow
# to set arbitrary headers.
# Preceding the domain with '~' character allows access to that domain only
# (including all paths within that domain), but does not allow access to links
# to other, outside domains. Sites that are added dynamically by trusted
# referrers will include the '~' character, and thus do not become trusted
# referrers themselves.
# Example: to allow example.com and to white-list domains that appear to
# be reached through links from example.com, uncomment this line:
# +example.com
# The next two lines make sure that the user can access Privoxy's
# CGI pages, without automatically trusting their links.
~config.privoxy.org
~p.p
|
