From ff9386cc783d0e77c145e5dc33a1f7243df5c6ee Mon Sep 17 00:00:00 2001 From: Fabian Keil Date: Sat, 6 Nov 2021 13:50:49 +0100 Subject: [PATCH] Regenerate config file --- config | 37 +++++++++++++++++++++++++++++-------- 1 file changed, 29 insertions(+), 8 deletions(-) diff --git a/config b/config index b65e6f37..e0434e25 100644 --- a/config +++ b/config @@ -1896,6 +1896,15 @@ tolerate-pipelining 1 # If you aren't using an occasionally slow proxy like Tor, # reducing it to a few seconds should be fine. # +# +-----------------------------------------------------+ +# | Warning | +# |-----------------------------------------------------| +# |When a TLS library is being used to read or write | +# |data from a socket with https-inspection enabled the | +# |socket-timeout currently isn't applied and the | +# |timeout used depends on the library (which may not | +# |even use a timeout). | +# +-----------------------------------------------------+ # Example: # # socket-timeout 300 @@ -1950,11 +1959,15 @@ socket-timeout 300 # limit below the one enforced by the operating system. # # One most POSIX-compliant systems Privoxy can't properly deal -# with more than FD_SETSIZE file descriptors at the same time -# and has to reject connections if the limit is reached. This -# will likely change in a future version, but currently this -# limit can't be increased without recompiling Privoxy with a -# different FD_SETSIZE limit. +# with more than FD_SETSIZE file descriptors if Privoxy has been +# configured to use select() and has to reject connections if +# the limit is reached. When using select() this limit therefore +# can't be increased without recompiling Privoxy with a +# different FD_SETSIZE limit unless Privoxy is running on +# Windows with _WIN32 defined. +# +# When Privoxy has been configured to use poll() the FD_SETSIZE +# limit does not apply. # # Example: # @@ -2565,9 +2578,17 @@ socket-timeout 300 # is used when Privoxy generates certificates for intercepted # requests. # -# Note that the password is shown on the CGI page so don't reuse -# an important one. -# +# +-----------------------------------------------------+ +# | Warning | +# |-----------------------------------------------------| +# |Note that the password is shown on the CGI page so | +# |don't reuse an important one. | +# | | +# |If disclosure of the password is a compliance issue | +# |consider blocking the relevant CGI requests after | +# |enabling the enforce-blocks and | +# |allow-cgi-request-crunching. | +# +-----------------------------------------------------+ # Example: # # ca-password blafasel -- 2.39.2