ho installato tor e non mi funziona internet
- mrsocotra
- Prode Principiante
- Messaggi: 229
- Iscrizione: martedì 29 aprile 2008, 18:59
- Località: Genova
ho installato tor e non mi funziona internet
ho installato tor ma quando lo attivo con il tor button non mi naviga e sta fermo sulla pagina dalla quale lo ho attivato.
suggerimenti? grazie.
suggerimenti? grazie.
- alberto t.
- Imperturbabile Insigne

- Messaggi: 2977
- Iscrizione: domenica 10 febbraio 2008, 17:52
- mrsocotra
- Prode Principiante
- Messaggi: 229
- Iscrizione: martedì 29 aprile 2008, 18:59
- Località: Genova
Re: ho installato tor e non mi funziona internet
l'ho seguita ma il problema persiste, allego il file di config
Ho tagliato l'inizio perchè se no non stava in un messaggio
#
# 3. DEBUGGING
#
# These options are mainly useful when tracing a problem. Note that
# you might also want to invoke Privoxy with the --no-daemon command
# line option when debugging.
#
#
#
# 3.1. debug
#
# Specifies:
#
# Key values that determine what information gets logged.
#
# Type of value:
#
# Integer values
#
# Default value:
#
# 0 (i.e.: only fatal errors (that cause Privoxy to exit) are logged)
#
# Effect if unset:
#
# Default value is used (see above).
#
# Notes:
#
# The available debug levels are:
#
# debug 1 # log each request destination (and the crunch reason if Privoxy intercepted the request)
# debug 2 # show each connection status
# debug 4 # show I/O status
# debug 8 # show header parsing
# debug 16 # log all data written to the network into the logfile
# debug 32 # debug force feature
# debug 64 # debug regular expression filters
# debug 128 # debug redirects
# debug 256 # debug GIF de-animation
# debug 512 # Common Log Format
# debug 1024 # debug kill pop-ups
# debug 2048 # CGI user interface
# debug 4096 # Startup banner and warnings.
# debug 8192 # Non-fatal errors
#
#
# To select multiple debug levels, you can either add them or
# use multiple debug lines.
#
# A debug level of 1 is informative because it will show you each
# request as it happens. 1, 4096 and 8192 are recommended so that you
# will notice when things go wrong. The other levels are probably only
# of interest if you are hunting down a specific problem. They can
# produce a hell of an output (especially 16).
#
# Privoxy used to ship with the debug levels recommended above enabled
# by default, but due to privacy concerns 3.0.7 and later are
# configured to only log fatal errors.
#
# If you are used to the more verbose settings, simply enable the debug
# lines below again.
#
# If you want to use pure CLF (Common Log Format), you should set
# debug 512 ONLY and not enable anything else.
#
# Privoxy has a hard-coded limit for the length of log messages. If
# it's reached, messages are logged truncated and marked with
# "... [too long, truncated]".
#
# Please don't file any support requests without trying to reproduce
# the problem with increased debug level first. Once you read the log
# messages, you may even be able to solve the problem on your own.
#
#debug 1 # log each request destination (and the crunch reason if Privoxy intercepted the request)
#debug 4096 # Startup banner and warnings
#debug 8192 # Non-fatal errors
#
#
# 3.2. single-threaded
#
# Specifies:
#
# Whether to run only one server thread.
#
# Type of value:
#
# None
#
# Default value:
#
# Unset
#
# Effect if unset:
#
# Multi-threaded (or, where unavailable: forked) operation,
# i.e. the ability to serve multiple requests simultaneously.
#
# Notes:
#
# This option is only there for debugging purposes. It will
# drastically reduce performance.
#
#single-threaded
#
#
# 4. ACCESS CONTROL AND SECURITY
#
# This section of the config file controls the security-relevant
# aspects of Privoxy's configuration.
#
#
#
# 4.1. listen-address
#
# Specifies:
#
# The IP address and TCP port on which Privoxy will listen for
# client requests.
#
# Type of value:
#
# [IP-Address]:Port
#
# Default value:
#
# 127.0.0.1:8118
#
# Effect if unset:
#
# Bind to 127.0.0.1 (localhost), port 8118. This is suitable and
# recommended for home users who run Privoxy on the same machine
# as their browser.
#
# Notes:
#
# You will need to configure your browser(s) to this proxy address
# and port.
#
# If you already have another service running on port 8118, or
# if you want to serve requests from other machines (e.g. on your
# local network) as well, you will need to override the default.
#
# If you leave out the IP address, Privoxy will bind to all
# interfaces (addresses) on your machine and may become reachable
# from the Internet. In that case, consider using access control
# lists (ACL's, see below), and/or a firewall.
#
# If you open Privoxy to untrusted users, you will also
# want to make sure that the following actions are disabled:
# enable-edit-actions and enable-remote-toggle
#
# Example:
#
# Suppose you are running Privoxy on a machine which has the
# address 192.168.0.1 on your local private network (192.168.0.0)
# and has another outside connection with a different address. You
# want it to serve requests from inside only:
#
# listen-address 192.168.0.1:8118
#
#
listen-address 127.0.0.1:8118
#
#
# 4.2. toggle
#
# Specifies:
#
# Initial state of "toggle" status
#
# Type of value:
#
# 1 or 0
#
# Default value:
#
# 1
#
# Effect if unset:
#
# Act as if toggled on
#
# Notes:
#
# If set to 0, Privoxy will start in "toggled off" mode,
# i.e. mostly behave like a normal, content-neutral proxy
# with both ad blocking and content filtering disabled. See
# enable-remote-toggle below.
#
# The windows version will only display the toggle icon in the
# system tray if this option is present.
#
toggle 1
#
#
# 4.3. enable-remote-toggle
#
# Specifies:
#
# Whether or not the web-based toggle feature may be used
#
# Type of value:
#
# 0 or 1
#
# Default value:
#
# 0
#
# Effect if unset:
#
# The web-based toggle feature is disabled.
#
# Notes:
#
# When toggled off, Privoxy mostly acts like a normal,
# content-neutral proxy, i.e. doesn't block ads or filter content.
#
# Access to the toggle feature can not be controlled separately by
# "ACLs" or HTTP authentication, so that everybody who can access
# Privoxy (see "ACLs" and listen-address above) can toggle it
# for all users. So this option is not recommended for multi-user
# environments with untrusted users.
#
# Note that malicious client side code (e.g Java) is also capable
# of using this option.
#
# As a lot of Privoxy users don't read documentation, this feature
# is disabled by default.
#
# Note that you must have compiled Privoxy with support for this
# feature, otherwise this option has no effect.
#
enable-remote-toggle 0
#
#
# 4.4. enable-remote-http-toggle
#
# Specifies:
#
# Whether or not Privoxy recognizes special HTTP headers to change
# its behaviour.
#
# Type of value:
#
# 0 or 1
#
# Default value:
#
# 0
#
# Effect if unset:
#
# Privoxy ignores special HTTP headers.
#
# Notes:
#
# When toggled on, the client can change Privoxy's behaviour by
# setting special HTTP headers. Currently the only supported
# special header is "X-Filter: No", to disable filtering for
# the ongoing request, even if it is enabled in one of the
# action files.
#
# This feature is disabled by default. If you are using Privoxy in
# a environment with trusted clients, you may enable this feature
# at your discretion. Note that malicious client side code (e.g
# Java) is also capable of using this feature.
#
# This option will be removed in future releases as it has been
# obsoleted by the more general header taggers.
#
enable-remote-http-toggle 0
#
#
# 4.5. enable-edit-actions
#
# Specifies:
#
# Whether or not the web-based actions file editor may be used
#
# Type of value:
#
# 0 or 1
#
# Default value:
#
# 0
#
# Effect if unset:
#
# The web-based actions file editor is disabled.
#
# Notes:
#
# Access to the editor can not be controlled separately by
# "ACLs" or HTTP authentication, so that everybody who can access
# Privoxy (see "ACLs" and listen-address above) can modify its
# configuration for all users.
#
# This option is not recommended for environments with untrusted
# users and as a lot of Privoxy users don't read documentation,
# this feature is disabled by default.
#
# Note that malicious client side code (e.g Java) is also capable
# of using the actions editor and you shouldn't enable this
# options unless you understand the consequences and are sure
# your browser is configured correctly.
#
# Note that you must have compiled Privoxy with support for this
# feature, otherwise this option has no effect.
#
enable-edit-actions 0
#
#
# 4.6. enforce-blocks
#
# Specifies:
#
# Whether the user is allowed to ignore blocks and can "go there
# anyway".
#
# Type of value:
#
# 0 or 1
#
# Default value:
#
# 0
#
# Effect if unset:
#
# Blocks are not enforced.
#
# Notes:
#
# Privoxy is mainly used to block and filter requests as a service
# to the user, for example to block ads and other junk that clogs
# the pipes. Privoxy's configuration isn't perfect and sometimes
# innocent pages are blocked. In this situation it makes sense to
# allow the user to enforce the request and have Privoxy ignore
# the block.
#
# In the default configuration Privoxy's "Blocked" page contains
# a "go there anyway" link to adds a special string (the force
# prefix) to the request URL. If that link is used, Privoxy
# will detect the force prefix, remove it again and let the
# request pass.
#
# Of course Privoxy can also be used to enforce a network
# policy. In that case the user obviously should not be able to
# bypass any blocks, and that's what the "enforce-blocks" option
# is for. If it's enabled, Privoxy hides the "go there anyway"
# link. If the user adds the force prefix by hand, it will not
# be accepted and the circumvention attempt is logged.
#
# Examples:
#
# enforce-blocks 1
#
enforce-blocks 0
#
#
# 4.7. ACLs: permit-access and deny-access
#
# Specifies:
#
# Who can access what.
#
# Type of value:
#
# src_addr[/src_masklen] [dst_addr[/dst_masklen]]
#
# Where src_addr and dst_addr are IP addresses in dotted decimal
# notation or valid DNS names, and src_masklen and dst_masklen are
# subnet masks in CIDR notation, i.e. integer values from 2 to 30
# representing the length (in bits) of the network address. The
# masks and the whole destination part are optional.
#
# Default value:
#
# Unset
#
# Effect if unset:
#
# Don't restrict access further than implied by listen-address
#
# Notes:
#
# Access controls are included at the request of ISPs and systems
# administrators, and are not usually needed by individual
# users. For a typical home user, it will normally suffice to
# ensure that Privoxy only listens on the localhost (127.0.0.1)
# or internal (home) network address by means of the listen-address
# option.
#
# Please see the warnings in the FAQ that Privoxy is not intended
# to be a substitute for a firewall or to encourage anyone to
# defer addressing basic security weaknesses.
#
# Multiple ACL lines are OK. If any ACLs are specified, Privoxy
# only talks to IP addresses that match at least one permit-access
# line and don't match any subsequent deny-access line. In other
# words, the last match wins, with the default being deny-access.
#
# If Privoxy is using a forwarder (see forward below) for a
# particular destination URL, the dst_addr that is examined is
# the address of the forwarder and NOT the address of the ultimate
# target. This is necessary because it may be impossible for the
# local Privoxy to determine the IP address of the ultimate target
# (that's often what gateways are used for).
#
# You should prefer using IP addresses over DNS names, because
# the address lookups take time. All DNS names must resolve! You
# can not use domain patterns like "*.org" or partial domain
# names. If a DNS name resolves to multiple IP addresses, only
# the first one is used.
#
# Denying access to particular sites by ACL may have undesired
# side effects if the site in question is hosted on a machine
# which also hosts other sites (most sites are).
#
# Examples:
#
# Explicitly define the default behavior if no ACL and
# listen-address are set: "localhost" is OK. The absence of a
# dst_addr implies that all destination addresses are OK:
#
# permit-access localhost
#
#
# Allow any host on the same class C subnet as www.privoxy.org
# access to nothing but www.example.com (or other domains hosted
# on the same system):
#
# permit-access www.privoxy.org/24 www.example.com/32
#
#
# Allow access from any host on the 26-bit subnet 192.168.45.64 to
# anywhere, with the exception that 192.168.45.73 may not access
# the IP address behind www.dirty-stuff.example.com:
#
# permit-access 192.168.45.64/26
# deny-access 192.168.45.73 www.dirty-stuff.example.com
#
#
#
# 4.8. buffer-limit
#
# Specifies:
#
# Maximum size of the buffer for content filtering.
#
# Type of value:
#
# Size in Kbytes
#
# Default value:
#
# 4096
#
# Effect if unset:
#
# Use a 4MB (4096 KB) limit.
#
# Notes:
#
# For content filtering, i.e. the +filter and +deanimate-gif
# actions, it is necessary that Privoxy buffers the entire document
# body. This can be potentially dangerous, since a server could
# just keep sending data indefinitely and wait for your RAM to
# exhaust -- with nasty consequences. Hence this option.
#
# When a document buffer size reaches the buffer-limit, it is
# flushed to the client unfiltered and no further attempt to filter
# the rest of the document is made. Remember that there may be
# multiple threads running, which might require up to buffer-limit
# Kbytes each, unless you have enabled "single-threaded" above.
#
buffer-limit 4096
#
#
# 5. FORWARDING
#
# This feature allows routing of HTTP requests through a chain of
# multiple proxies.
#
# Forwarding can be used to chain Privoxy with a caching proxy to
# speed up browsing. Using a parent proxy may also be necessary if
# the machine that Privoxy runs on has no direct Internet access.
#
# Note that parent proxies can severely decrease your privacy
# level. For example a parent proxy could add your IP address to the
# request headers and if it's a caching proxy it may add the "Etag"
# header to revalidation requests again, even though you configured
# Privoxy to remove it. It may also ignore Privoxy's header time
# randomization and use the original values which could be used by
# the server as cookie replacement to track your steps between visits.
#
# Also specified here are SOCKS proxies. Privoxy supports the SOCKS
# 4 and SOCKS 4A protocols.
#
#
#
# 5.1. forward
#
# Specifies:
#
# To which parent HTTP proxy specific requests should be routed.
#
# Type of value:
#
# target_pattern http_parent[:port]
#
# where target_pattern is a URL pattern that specifies to which
# requests (i.e. URLs) this forward rule shall apply. Use /
# to denote "all URLs". http_parent[:port] is the DNS name or
# IP address of the parent HTTP proxy through which the requests
# should be forwarded, optionally followed by its listening port
# (default: 8080). Use a single dot (.) to denote "no forwarding".
#
# Default value:
#
# Unset
#
# Effect if unset:
#
# Don't use parent HTTP proxies.
#
# Notes:
#
# If http_parent is ".", then requests are not forwarded to
# another HTTP proxy but are made directly to the web servers.
#
# Multiple lines are OK, they are checked in sequence, and the
# last match wins.
#
# Examples:
#
# Everything goes to an example parent proxy, except SSL on port
# 443 (which it doesn't handle):
#
# forward / parent-proxy.example.org:8080
# forward :443 .
#
#
# Everything goes to our example ISP's caching proxy, except for
# requests to that ISP's sites:
#
# forward / caching-proxy.isp.example.net:8000
# forward .isp.example.net .
#
#
#
#
# 5.2. forward-socks4 and forward-socks4a
#
# Specifies:
#
# Through which SOCKS proxy (and optionally to which parent HTTP
# proxy) specific requests should be routed.
#
# Type of value:
#
# target_pattern socks_proxy[:port] http_parent[:port]
#
# where target_pattern is a URL pattern that specifies to which
# requests (i.e. URLs) this forward rule shall apply. Use / to
# denote "all URLs". http_parent and socks_proxy are IP addresses
# in dotted decimal notation or valid DNS names (http_parent may
# be "." to denote "no HTTP forwarding"), and the optional port
# parameters are TCP ports, i.e. integer values from 1 to 64535
#
# Default value:
#
# Unset
#
# Effect if unset:
#
# Don't use SOCKS proxies.
#
# Notes:
#
# Multiple lines are OK, they are checked in sequence, and the
# last match wins.
#
# The difference between forward-socks4 and forward-socks4a
# is that in the SOCKS 4A protocol, the DNS resolution of the
# target hostname happens on the SOCKS server, while in SOCKS 4
# it happens locally.
#
# If http_parent is ".", then requests are not forwarded to another
# HTTP proxy but are made (HTTP-wise) directly to the web servers,
# albeit through a SOCKS proxy.
#
# Examples:
#
# From the company example.com, direct connections are made to all
# "internal" domains, but everything outbound goes through their
# ISP's proxy by way of example.com's corporate SOCKS 4A gateway
# to the Internet.
#
# forward-socks4a / socks-gw.example.com:1080 www-cache.isp.example.net:8080
# forward .example.com .
#
#
# A rule that uses a SOCKS 4 gateway for all destinations but no
# HTTP parent looks like this:
#
# forward-socks4 / socks-gw.example.com:1080 .
#
#
# To chain Privoxy and Tor, both running on the same system,
# you would use something like:
#
# forward-socks4a / 127.0.0.1:9050 .
#
#
# The public Tor network can't be used to reach your local network,
# if you need to access local servers you therefore might want
# to make some exceptions:
#
# forward 192.168.*.*/ .
# forward 10.*.*.*/ .
# forward 127.*.*.*/ .
#
#
# Unencrypted connections to systems in these address ranges will
# be as (un) secure as the local network is, but the alternative
# is that you can't reach the local network through Privoxy at
# all. Of course this may actually be desired and there is no
# reason to make these exceptions if you aren't sure you need them.
#
# If you also want to be able to reach servers in your local
# network by using their names, you will need additional exceptions
# that look like this:
#
# forward localhost/ .
#
#
#
#
# 5.3. forwarded-connect-retries
#
# Specifies:
#
# How often Privoxy retries if a forwarded connection request
# fails.
#
# Type of value:
#
# Number of retries.
#
# Default value:
#
# 0
#
# Effect if unset:
#
# Connections forwarded through other proxies are treated like
# direct connections and no retry attempts are made.
#
# Notes:
#
# forwarded-connect-retries is mainly interesting for socks4a
# connections, where Privoxy can't detect why the connections
# failed. The connection might have failed because of a DNS timeout
# in which case a retry makes sense, but it might also have failed
# because the server doesn't exist or isn't reachable. In this
# case the retry will just delay the appearance of Privoxy's
# error message.
#
# Note that in the context of this option, "forwarded connections"
# includes all connections that Privoxy forwards through other
# proxies. This option is not limited to the HTTP CONNECT method.
#
# Only use this option, if you are getting lots of
# forwarding-related error messages that go away when you try again
# manually. Start with a small value and check Privoxy's logfile
# from time to time, to see how many retries are usually needed.
#
# Examples:
#
# forwarded-connect-retries 1
#
forwarded-connect-retries 0
#
#
# 5.4. accept-intercepted-requests
#
# Specifies:
#
# Whether intercepted requests should be treated as valid.
#
# Type of value:
#
# 0 or 1
#
# Default value:
#
# 0
#
# Effect if unset:
#
# Only proxy requests are accepted, intercepted requests are
# treated as invalid.
#
# Notes:
#
# If you don't trust your clients and want to force them to use
# Privoxy, enable this option and configure your packet filter
# to redirect outgoing HTTP connections into Privoxy.
#
# Make sure that Privoxy's own requests aren't redirected as well.
# Additionally take care that Privoxy can't intentionally connect
# to itself, otherwise you could run into redirection loops if
# Privoxy's listening port is reachable by the outside or an
# attacker has access to the pages you visit.
#
# Examples:
#
# accept-intercepted-requests 1
#
accept-intercepted-requests 0
#
#
# 5.5. allow-cgi-request-crunching
#
# Specifies:
#
# Whether requests to Privoxy's CGI pages can be blocked or
# redirected.
#
# Type of value:
#
# 0 or 1
#
# Default value:
#
# 0
#
# Effect if unset:
#
# Privoxy ignores block and redirect actions for its CGI pages.
#
# Notes:
#
# By default Privoxy ignores block or redirect actions for
# its CGI pages. Intercepting these requests can be useful in
# multi-user setups to implement fine-grained access control,
# but it can also render the complete web interface useless and
# make debugging problems painful if done without care.
#
# Don't enable this option unless you're sure that you really
# need it.
#
# Examples:
#
# allow-cgi-request-crunching 1
#
allow-cgi-request-crunching 0
#
#
# 5.6. split-large-forms
#
# Specifies:
#
# Whether the CGI interface should stay compatible with broken
# HTTP clients.
#
# Type of value:
#
# 0 or 1
#
# Default value:
#
# 0
#
# Effect if unset:
#
# The CGI form generate long GET URLs.
#
# Notes:
#
# Privoxy's CGI forms can lead to rather long URLs. This isn't
# a problem as far as the HTTP standard is concerned, but it can
# confuse clients with arbitrary URL length limitations.
#
# Enabling split-large-forms causes Privoxy to divide big forms
# into smaller ones to keep the URL length down. It makes editing
# a lot less convenient and you can no longer submit all changes
# at once, but at least it works around this browser bug.
#
# If you don't notice any editing problems, there is no reason
# to enable this option, but if one of the submit buttons appears
# to be broken, you should give it a try.
#
# Examples:
#
# split-large-forms 1
#
split-large-forms 0
#
#
# 6. WINDOWS GUI OPTIONS
#
# Privoxy has a number of options specific to the Windows GUI
# interface:
#
# If "activity-animation" is set to 1, the Privoxy icon will animate
# when "Privoxy" is active. To turn off, set to 0.
#
#activity-animation 1
# If "log-messages" is set to 1, Privoxy will log messages to the
# console window:
#
#log-messages 1
# If "log-buffer-size" is set to 1, the size of the log buffer,
# i.e. the amount of memory used for the log messages displayed in
# the console window, will be limited to "log-max-lines" (see below).
#
# Warning: Setting this to 0 will result in the buffer to grow
# infinitely and eat up all your memory!
#
#log-buffer-size 1
# log-max-lines is the maximum number of lines held in the log
# buffer. See above.
#
#log-max-lines 200
# If "log-highlight-messages" is set to 1, Privoxy will highlight
# portions of the log messages with a bold-faced font:
#
#log-highlight-messages 1
# The font used in the console window:
#
#log-font-name Comic Sans MS
# Font size used in the console window:
#
#log-font-size 8
# "show-on-task-bar" controls whether or not Privoxy will appear as
# a button on the Task bar when minimized:
#
#show-on-task-bar 0
# If "close-button-minimizes" is set to 1, the Windows close button
# will minimize Privoxy instead of closing the program (close with
# the exit option on the File menu).
#
#close-button-minimizes 1
# The "hide-console" option is specific to the MS-Win console version
# of Privoxy. If this option is used, Privoxy will disconnect from
# and hide the command console.
#
#hide-console
#
#logfile logfile
#jarfile jarfile
#forward-socks4a / localhost:9050 .
Ho tagliato l'inizio perchè se no non stava in un messaggio
#
# 3. DEBUGGING
#
# These options are mainly useful when tracing a problem. Note that
# you might also want to invoke Privoxy with the --no-daemon command
# line option when debugging.
#
#
#
# 3.1. debug
#
# Specifies:
#
# Key values that determine what information gets logged.
#
# Type of value:
#
# Integer values
#
# Default value:
#
# 0 (i.e.: only fatal errors (that cause Privoxy to exit) are logged)
#
# Effect if unset:
#
# Default value is used (see above).
#
# Notes:
#
# The available debug levels are:
#
# debug 1 # log each request destination (and the crunch reason if Privoxy intercepted the request)
# debug 2 # show each connection status
# debug 4 # show I/O status
# debug 8 # show header parsing
# debug 16 # log all data written to the network into the logfile
# debug 32 # debug force feature
# debug 64 # debug regular expression filters
# debug 128 # debug redirects
# debug 256 # debug GIF de-animation
# debug 512 # Common Log Format
# debug 1024 # debug kill pop-ups
# debug 2048 # CGI user interface
# debug 4096 # Startup banner and warnings.
# debug 8192 # Non-fatal errors
#
#
# To select multiple debug levels, you can either add them or
# use multiple debug lines.
#
# A debug level of 1 is informative because it will show you each
# request as it happens. 1, 4096 and 8192 are recommended so that you
# will notice when things go wrong. The other levels are probably only
# of interest if you are hunting down a specific problem. They can
# produce a hell of an output (especially 16).
#
# Privoxy used to ship with the debug levels recommended above enabled
# by default, but due to privacy concerns 3.0.7 and later are
# configured to only log fatal errors.
#
# If you are used to the more verbose settings, simply enable the debug
# lines below again.
#
# If you want to use pure CLF (Common Log Format), you should set
# debug 512 ONLY and not enable anything else.
#
# Privoxy has a hard-coded limit for the length of log messages. If
# it's reached, messages are logged truncated and marked with
# "... [too long, truncated]".
#
# Please don't file any support requests without trying to reproduce
# the problem with increased debug level first. Once you read the log
# messages, you may even be able to solve the problem on your own.
#
#debug 1 # log each request destination (and the crunch reason if Privoxy intercepted the request)
#debug 4096 # Startup banner and warnings
#debug 8192 # Non-fatal errors
#
#
# 3.2. single-threaded
#
# Specifies:
#
# Whether to run only one server thread.
#
# Type of value:
#
# None
#
# Default value:
#
# Unset
#
# Effect if unset:
#
# Multi-threaded (or, where unavailable: forked) operation,
# i.e. the ability to serve multiple requests simultaneously.
#
# Notes:
#
# This option is only there for debugging purposes. It will
# drastically reduce performance.
#
#single-threaded
#
#
# 4. ACCESS CONTROL AND SECURITY
#
# This section of the config file controls the security-relevant
# aspects of Privoxy's configuration.
#
#
#
# 4.1. listen-address
#
# Specifies:
#
# The IP address and TCP port on which Privoxy will listen for
# client requests.
#
# Type of value:
#
# [IP-Address]:Port
#
# Default value:
#
# 127.0.0.1:8118
#
# Effect if unset:
#
# Bind to 127.0.0.1 (localhost), port 8118. This is suitable and
# recommended for home users who run Privoxy on the same machine
# as their browser.
#
# Notes:
#
# You will need to configure your browser(s) to this proxy address
# and port.
#
# If you already have another service running on port 8118, or
# if you want to serve requests from other machines (e.g. on your
# local network) as well, you will need to override the default.
#
# If you leave out the IP address, Privoxy will bind to all
# interfaces (addresses) on your machine and may become reachable
# from the Internet. In that case, consider using access control
# lists (ACL's, see below), and/or a firewall.
#
# If you open Privoxy to untrusted users, you will also
# want to make sure that the following actions are disabled:
# enable-edit-actions and enable-remote-toggle
#
# Example:
#
# Suppose you are running Privoxy on a machine which has the
# address 192.168.0.1 on your local private network (192.168.0.0)
# and has another outside connection with a different address. You
# want it to serve requests from inside only:
#
# listen-address 192.168.0.1:8118
#
#
listen-address 127.0.0.1:8118
#
#
# 4.2. toggle
#
# Specifies:
#
# Initial state of "toggle" status
#
# Type of value:
#
# 1 or 0
#
# Default value:
#
# 1
#
# Effect if unset:
#
# Act as if toggled on
#
# Notes:
#
# If set to 0, Privoxy will start in "toggled off" mode,
# i.e. mostly behave like a normal, content-neutral proxy
# with both ad blocking and content filtering disabled. See
# enable-remote-toggle below.
#
# The windows version will only display the toggle icon in the
# system tray if this option is present.
#
toggle 1
#
#
# 4.3. enable-remote-toggle
#
# Specifies:
#
# Whether or not the web-based toggle feature may be used
#
# Type of value:
#
# 0 or 1
#
# Default value:
#
# 0
#
# Effect if unset:
#
# The web-based toggle feature is disabled.
#
# Notes:
#
# When toggled off, Privoxy mostly acts like a normal,
# content-neutral proxy, i.e. doesn't block ads or filter content.
#
# Access to the toggle feature can not be controlled separately by
# "ACLs" or HTTP authentication, so that everybody who can access
# Privoxy (see "ACLs" and listen-address above) can toggle it
# for all users. So this option is not recommended for multi-user
# environments with untrusted users.
#
# Note that malicious client side code (e.g Java) is also capable
# of using this option.
#
# As a lot of Privoxy users don't read documentation, this feature
# is disabled by default.
#
# Note that you must have compiled Privoxy with support for this
# feature, otherwise this option has no effect.
#
enable-remote-toggle 0
#
#
# 4.4. enable-remote-http-toggle
#
# Specifies:
#
# Whether or not Privoxy recognizes special HTTP headers to change
# its behaviour.
#
# Type of value:
#
# 0 or 1
#
# Default value:
#
# 0
#
# Effect if unset:
#
# Privoxy ignores special HTTP headers.
#
# Notes:
#
# When toggled on, the client can change Privoxy's behaviour by
# setting special HTTP headers. Currently the only supported
# special header is "X-Filter: No", to disable filtering for
# the ongoing request, even if it is enabled in one of the
# action files.
#
# This feature is disabled by default. If you are using Privoxy in
# a environment with trusted clients, you may enable this feature
# at your discretion. Note that malicious client side code (e.g
# Java) is also capable of using this feature.
#
# This option will be removed in future releases as it has been
# obsoleted by the more general header taggers.
#
enable-remote-http-toggle 0
#
#
# 4.5. enable-edit-actions
#
# Specifies:
#
# Whether or not the web-based actions file editor may be used
#
# Type of value:
#
# 0 or 1
#
# Default value:
#
# 0
#
# Effect if unset:
#
# The web-based actions file editor is disabled.
#
# Notes:
#
# Access to the editor can not be controlled separately by
# "ACLs" or HTTP authentication, so that everybody who can access
# Privoxy (see "ACLs" and listen-address above) can modify its
# configuration for all users.
#
# This option is not recommended for environments with untrusted
# users and as a lot of Privoxy users don't read documentation,
# this feature is disabled by default.
#
# Note that malicious client side code (e.g Java) is also capable
# of using the actions editor and you shouldn't enable this
# options unless you understand the consequences and are sure
# your browser is configured correctly.
#
# Note that you must have compiled Privoxy with support for this
# feature, otherwise this option has no effect.
#
enable-edit-actions 0
#
#
# 4.6. enforce-blocks
#
# Specifies:
#
# Whether the user is allowed to ignore blocks and can "go there
# anyway".
#
# Type of value:
#
# 0 or 1
#
# Default value:
#
# 0
#
# Effect if unset:
#
# Blocks are not enforced.
#
# Notes:
#
# Privoxy is mainly used to block and filter requests as a service
# to the user, for example to block ads and other junk that clogs
# the pipes. Privoxy's configuration isn't perfect and sometimes
# innocent pages are blocked. In this situation it makes sense to
# allow the user to enforce the request and have Privoxy ignore
# the block.
#
# In the default configuration Privoxy's "Blocked" page contains
# a "go there anyway" link to adds a special string (the force
# prefix) to the request URL. If that link is used, Privoxy
# will detect the force prefix, remove it again and let the
# request pass.
#
# Of course Privoxy can also be used to enforce a network
# policy. In that case the user obviously should not be able to
# bypass any blocks, and that's what the "enforce-blocks" option
# is for. If it's enabled, Privoxy hides the "go there anyway"
# link. If the user adds the force prefix by hand, it will not
# be accepted and the circumvention attempt is logged.
#
# Examples:
#
# enforce-blocks 1
#
enforce-blocks 0
#
#
# 4.7. ACLs: permit-access and deny-access
#
# Specifies:
#
# Who can access what.
#
# Type of value:
#
# src_addr[/src_masklen] [dst_addr[/dst_masklen]]
#
# Where src_addr and dst_addr are IP addresses in dotted decimal
# notation or valid DNS names, and src_masklen and dst_masklen are
# subnet masks in CIDR notation, i.e. integer values from 2 to 30
# representing the length (in bits) of the network address. The
# masks and the whole destination part are optional.
#
# Default value:
#
# Unset
#
# Effect if unset:
#
# Don't restrict access further than implied by listen-address
#
# Notes:
#
# Access controls are included at the request of ISPs and systems
# administrators, and are not usually needed by individual
# users. For a typical home user, it will normally suffice to
# ensure that Privoxy only listens on the localhost (127.0.0.1)
# or internal (home) network address by means of the listen-address
# option.
#
# Please see the warnings in the FAQ that Privoxy is not intended
# to be a substitute for a firewall or to encourage anyone to
# defer addressing basic security weaknesses.
#
# Multiple ACL lines are OK. If any ACLs are specified, Privoxy
# only talks to IP addresses that match at least one permit-access
# line and don't match any subsequent deny-access line. In other
# words, the last match wins, with the default being deny-access.
#
# If Privoxy is using a forwarder (see forward below) for a
# particular destination URL, the dst_addr that is examined is
# the address of the forwarder and NOT the address of the ultimate
# target. This is necessary because it may be impossible for the
# local Privoxy to determine the IP address of the ultimate target
# (that's often what gateways are used for).
#
# You should prefer using IP addresses over DNS names, because
# the address lookups take time. All DNS names must resolve! You
# can not use domain patterns like "*.org" or partial domain
# names. If a DNS name resolves to multiple IP addresses, only
# the first one is used.
#
# Denying access to particular sites by ACL may have undesired
# side effects if the site in question is hosted on a machine
# which also hosts other sites (most sites are).
#
# Examples:
#
# Explicitly define the default behavior if no ACL and
# listen-address are set: "localhost" is OK. The absence of a
# dst_addr implies that all destination addresses are OK:
#
# permit-access localhost
#
#
# Allow any host on the same class C subnet as www.privoxy.org
# access to nothing but www.example.com (or other domains hosted
# on the same system):
#
# permit-access www.privoxy.org/24 www.example.com/32
#
#
# Allow access from any host on the 26-bit subnet 192.168.45.64 to
# anywhere, with the exception that 192.168.45.73 may not access
# the IP address behind www.dirty-stuff.example.com:
#
# permit-access 192.168.45.64/26
# deny-access 192.168.45.73 www.dirty-stuff.example.com
#
#
#
# 4.8. buffer-limit
#
# Specifies:
#
# Maximum size of the buffer for content filtering.
#
# Type of value:
#
# Size in Kbytes
#
# Default value:
#
# 4096
#
# Effect if unset:
#
# Use a 4MB (4096 KB) limit.
#
# Notes:
#
# For content filtering, i.e. the +filter and +deanimate-gif
# actions, it is necessary that Privoxy buffers the entire document
# body. This can be potentially dangerous, since a server could
# just keep sending data indefinitely and wait for your RAM to
# exhaust -- with nasty consequences. Hence this option.
#
# When a document buffer size reaches the buffer-limit, it is
# flushed to the client unfiltered and no further attempt to filter
# the rest of the document is made. Remember that there may be
# multiple threads running, which might require up to buffer-limit
# Kbytes each, unless you have enabled "single-threaded" above.
#
buffer-limit 4096
#
#
# 5. FORWARDING
#
# This feature allows routing of HTTP requests through a chain of
# multiple proxies.
#
# Forwarding can be used to chain Privoxy with a caching proxy to
# speed up browsing. Using a parent proxy may also be necessary if
# the machine that Privoxy runs on has no direct Internet access.
#
# Note that parent proxies can severely decrease your privacy
# level. For example a parent proxy could add your IP address to the
# request headers and if it's a caching proxy it may add the "Etag"
# header to revalidation requests again, even though you configured
# Privoxy to remove it. It may also ignore Privoxy's header time
# randomization and use the original values which could be used by
# the server as cookie replacement to track your steps between visits.
#
# Also specified here are SOCKS proxies. Privoxy supports the SOCKS
# 4 and SOCKS 4A protocols.
#
#
#
# 5.1. forward
#
# Specifies:
#
# To which parent HTTP proxy specific requests should be routed.
#
# Type of value:
#
# target_pattern http_parent[:port]
#
# where target_pattern is a URL pattern that specifies to which
# requests (i.e. URLs) this forward rule shall apply. Use /
# to denote "all URLs". http_parent[:port] is the DNS name or
# IP address of the parent HTTP proxy through which the requests
# should be forwarded, optionally followed by its listening port
# (default: 8080). Use a single dot (.) to denote "no forwarding".
#
# Default value:
#
# Unset
#
# Effect if unset:
#
# Don't use parent HTTP proxies.
#
# Notes:
#
# If http_parent is ".", then requests are not forwarded to
# another HTTP proxy but are made directly to the web servers.
#
# Multiple lines are OK, they are checked in sequence, and the
# last match wins.
#
# Examples:
#
# Everything goes to an example parent proxy, except SSL on port
# 443 (which it doesn't handle):
#
# forward / parent-proxy.example.org:8080
# forward :443 .
#
#
# Everything goes to our example ISP's caching proxy, except for
# requests to that ISP's sites:
#
# forward / caching-proxy.isp.example.net:8000
# forward .isp.example.net .
#
#
#
#
# 5.2. forward-socks4 and forward-socks4a
#
# Specifies:
#
# Through which SOCKS proxy (and optionally to which parent HTTP
# proxy) specific requests should be routed.
#
# Type of value:
#
# target_pattern socks_proxy[:port] http_parent[:port]
#
# where target_pattern is a URL pattern that specifies to which
# requests (i.e. URLs) this forward rule shall apply. Use / to
# denote "all URLs". http_parent and socks_proxy are IP addresses
# in dotted decimal notation or valid DNS names (http_parent may
# be "." to denote "no HTTP forwarding"), and the optional port
# parameters are TCP ports, i.e. integer values from 1 to 64535
#
# Default value:
#
# Unset
#
# Effect if unset:
#
# Don't use SOCKS proxies.
#
# Notes:
#
# Multiple lines are OK, they are checked in sequence, and the
# last match wins.
#
# The difference between forward-socks4 and forward-socks4a
# is that in the SOCKS 4A protocol, the DNS resolution of the
# target hostname happens on the SOCKS server, while in SOCKS 4
# it happens locally.
#
# If http_parent is ".", then requests are not forwarded to another
# HTTP proxy but are made (HTTP-wise) directly to the web servers,
# albeit through a SOCKS proxy.
#
# Examples:
#
# From the company example.com, direct connections are made to all
# "internal" domains, but everything outbound goes through their
# ISP's proxy by way of example.com's corporate SOCKS 4A gateway
# to the Internet.
#
# forward-socks4a / socks-gw.example.com:1080 www-cache.isp.example.net:8080
# forward .example.com .
#
#
# A rule that uses a SOCKS 4 gateway for all destinations but no
# HTTP parent looks like this:
#
# forward-socks4 / socks-gw.example.com:1080 .
#
#
# To chain Privoxy and Tor, both running on the same system,
# you would use something like:
#
# forward-socks4a / 127.0.0.1:9050 .
#
#
# The public Tor network can't be used to reach your local network,
# if you need to access local servers you therefore might want
# to make some exceptions:
#
# forward 192.168.*.*/ .
# forward 10.*.*.*/ .
# forward 127.*.*.*/ .
#
#
# Unencrypted connections to systems in these address ranges will
# be as (un) secure as the local network is, but the alternative
# is that you can't reach the local network through Privoxy at
# all. Of course this may actually be desired and there is no
# reason to make these exceptions if you aren't sure you need them.
#
# If you also want to be able to reach servers in your local
# network by using their names, you will need additional exceptions
# that look like this:
#
# forward localhost/ .
#
#
#
#
# 5.3. forwarded-connect-retries
#
# Specifies:
#
# How often Privoxy retries if a forwarded connection request
# fails.
#
# Type of value:
#
# Number of retries.
#
# Default value:
#
# 0
#
# Effect if unset:
#
# Connections forwarded through other proxies are treated like
# direct connections and no retry attempts are made.
#
# Notes:
#
# forwarded-connect-retries is mainly interesting for socks4a
# connections, where Privoxy can't detect why the connections
# failed. The connection might have failed because of a DNS timeout
# in which case a retry makes sense, but it might also have failed
# because the server doesn't exist or isn't reachable. In this
# case the retry will just delay the appearance of Privoxy's
# error message.
#
# Note that in the context of this option, "forwarded connections"
# includes all connections that Privoxy forwards through other
# proxies. This option is not limited to the HTTP CONNECT method.
#
# Only use this option, if you are getting lots of
# forwarding-related error messages that go away when you try again
# manually. Start with a small value and check Privoxy's logfile
# from time to time, to see how many retries are usually needed.
#
# Examples:
#
# forwarded-connect-retries 1
#
forwarded-connect-retries 0
#
#
# 5.4. accept-intercepted-requests
#
# Specifies:
#
# Whether intercepted requests should be treated as valid.
#
# Type of value:
#
# 0 or 1
#
# Default value:
#
# 0
#
# Effect if unset:
#
# Only proxy requests are accepted, intercepted requests are
# treated as invalid.
#
# Notes:
#
# If you don't trust your clients and want to force them to use
# Privoxy, enable this option and configure your packet filter
# to redirect outgoing HTTP connections into Privoxy.
#
# Make sure that Privoxy's own requests aren't redirected as well.
# Additionally take care that Privoxy can't intentionally connect
# to itself, otherwise you could run into redirection loops if
# Privoxy's listening port is reachable by the outside or an
# attacker has access to the pages you visit.
#
# Examples:
#
# accept-intercepted-requests 1
#
accept-intercepted-requests 0
#
#
# 5.5. allow-cgi-request-crunching
#
# Specifies:
#
# Whether requests to Privoxy's CGI pages can be blocked or
# redirected.
#
# Type of value:
#
# 0 or 1
#
# Default value:
#
# 0
#
# Effect if unset:
#
# Privoxy ignores block and redirect actions for its CGI pages.
#
# Notes:
#
# By default Privoxy ignores block or redirect actions for
# its CGI pages. Intercepting these requests can be useful in
# multi-user setups to implement fine-grained access control,
# but it can also render the complete web interface useless and
# make debugging problems painful if done without care.
#
# Don't enable this option unless you're sure that you really
# need it.
#
# Examples:
#
# allow-cgi-request-crunching 1
#
allow-cgi-request-crunching 0
#
#
# 5.6. split-large-forms
#
# Specifies:
#
# Whether the CGI interface should stay compatible with broken
# HTTP clients.
#
# Type of value:
#
# 0 or 1
#
# Default value:
#
# 0
#
# Effect if unset:
#
# The CGI form generate long GET URLs.
#
# Notes:
#
# Privoxy's CGI forms can lead to rather long URLs. This isn't
# a problem as far as the HTTP standard is concerned, but it can
# confuse clients with arbitrary URL length limitations.
#
# Enabling split-large-forms causes Privoxy to divide big forms
# into smaller ones to keep the URL length down. It makes editing
# a lot less convenient and you can no longer submit all changes
# at once, but at least it works around this browser bug.
#
# If you don't notice any editing problems, there is no reason
# to enable this option, but if one of the submit buttons appears
# to be broken, you should give it a try.
#
# Examples:
#
# split-large-forms 1
#
split-large-forms 0
#
#
# 6. WINDOWS GUI OPTIONS
#
# Privoxy has a number of options specific to the Windows GUI
# interface:
#
# If "activity-animation" is set to 1, the Privoxy icon will animate
# when "Privoxy" is active. To turn off, set to 0.
#
#activity-animation 1
# If "log-messages" is set to 1, Privoxy will log messages to the
# console window:
#
#log-messages 1
# If "log-buffer-size" is set to 1, the size of the log buffer,
# i.e. the amount of memory used for the log messages displayed in
# the console window, will be limited to "log-max-lines" (see below).
#
# Warning: Setting this to 0 will result in the buffer to grow
# infinitely and eat up all your memory!
#
#log-buffer-size 1
# log-max-lines is the maximum number of lines held in the log
# buffer. See above.
#
#log-max-lines 200
# If "log-highlight-messages" is set to 1, Privoxy will highlight
# portions of the log messages with a bold-faced font:
#
#log-highlight-messages 1
# The font used in the console window:
#
#log-font-name Comic Sans MS
# Font size used in the console window:
#
#log-font-size 8
# "show-on-task-bar" controls whether or not Privoxy will appear as
# a button on the Task bar when minimized:
#
#show-on-task-bar 0
# If "close-button-minimizes" is set to 1, the Windows close button
# will minimize Privoxy instead of closing the program (close with
# the exit option on the File menu).
#
#close-button-minimizes 1
# The "hide-console" option is specific to the MS-Win console version
# of Privoxy. If this option is used, Privoxy will disconnect from
# and hide the command console.
#
#hide-console
#
#logfile logfile
#jarfile jarfile
#forward-socks4a / localhost:9050 .
Re: ho installato tor e non mi funziona internet
se hai un router devi forwardare le porte che usa tor
inoltre la connessione sarà lenta, quindi aspetta un pò quando carichi le pagine
inoltre la connessione sarà lenta, quindi aspetta un pò quando carichi le pagine
- alberto t.
- Imperturbabile Insigne

- Messaggi: 2977
- Iscrizione: domenica 10 febbraio 2008, 17:52
Re: ho installato tor e non mi funziona internet
ciao
devi togliere il segno # davanti a:
Ciao, Alberto
devi togliere il segno # davanti a:
Codice: Seleziona tutto
forward-socks4a / localhost:9050 .- mrsocotra
- Prode Principiante
- Messaggi: 229
- Iscrizione: martedì 29 aprile 2008, 18:59
- Località: Genova
Re: ho installato tor e non mi funziona internet
fatto, ma non funziona lo stesso..
- mrsocotra
- Prode Principiante
- Messaggi: 229
- Iscrizione: martedì 29 aprile 2008, 18:59
- Località: Genova
Re: ho installato tor e non mi funziona internet
up.. appena clicco sulla cipollina rossa per farla diventare verde(se è una cipolla
) la connessione sembra bloccata e non mi carica più niente.
Chi c’è in linea
Visualizzano questa sezione: 0 utenti iscritti e 6 ospiti