trust 3.6 KB

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