| Privoxy 3.0.21 User Manual | +Privoxy 3.0.33 User Manual | ||||
|---|---|---|---|---|---|
| Prev | - +Prev | - - | Next | +Next | |
Privoxy 3.0.21 stable is a bug-fix - release for Privoxy 3.0.20 beta. It addresses two security issues that - affect all previous Privoxy versions. The changes since 3.0.20 beta - are:
- +Privoxy 3.0.33 fixes an XSS issue and multiple DoS issues and a couple of other + bugs. The issues also affect earlier Privoxy releases. Privoxy 3.0.33 also comes + with a couple of general improvements an new features.
+Changes in Privoxy 3.0.33 stable:
Bug fixes:
-On POSIX-like platforms, network sockets with file descriptor - values above FD_SETSIZE are properly rejected. Previously they - could cause memory corruption in configurations that allowed the - limit to be reached.
+handle_established_connection(): Skip the poll()/select() calls if TLS data is pending on the server + socket. The TLS library may have already consumed all the data from the server response in which case + poll() and select() will not detect that data is available to be read. Fixes SF bug #926 reported by Wen + Yue.
Proxy authentication headers are removed unless the new - directive enable-proxy-authentication-forwarding is used. - Forwarding the headers potentially allows malicious sites to - trick the user into providing them with login information. - Reported by Chris John Riley.
+continue_https_chat(): Update csp->server_connection.request_sent after sending the request to make + sure the latency is calculated correctly. Previously https connections were not reused after timeout + seconds after the first request made on the connection.
Compiles on OS/2 again now that unistd.h is only included on - platforms that have it.
+free_pattern_spec(): Don't try to free an invalid pointer when unloading an action file with a TAG + pattern while Privoxy has been compiled without FEATURE_PCRE_HOST_PATTERNS. Closes: SF patch request #147. + Patch by Maxim Antonov.
General improvements:
- -The show-status page shows the FEATURE_STRPTIME_SANITY_CHECKS - status.
-A couple of assert()s that could theoretically dereference - NULL pointers in debug builds have been relocated.
-Added an LSB info block to the generic start script. Based on - a patch from Natxo Asenjo.
-The max-client-connections default has been changed to 128 - which should be more than enough for most setups.
-Action file improvements:
- -Block rover.ebay./ar.*\&adtype= instead of - "/.*\&adtype=" which caused too man false positives. Reported - by u302320 in #360284, additional feedback from Adam Piggott.
-Unblock '.advrider.com/' and '/.*ADVrider'. Anonymously - reported in #3603636.
+Establish the TLS connection with the client earlier and decide how to route the request afterwards. + This allows to change the forwarding settings based on information from the https-inspected request, for + example the path.
Stop blocking '/js/slider\.js'. Reported by Adam Piggott in - #3606635 and _lvm in #2791160.
-Filter file improvements:
- -Added an iframes filter.
-Documentation improvements:
- -The whole GPLv2 text is included in the user manual now, so - Privoxy can serve it itself and the user can read it without - having to wade through GPLv3 ads first.
-Properly numbered and underlined a couple of section titles in - the config that where previously overlooked due to a flaw in the - conversion script. Reported by Ralf Jungblut.
-Improved the support instruction to hopefully make it harder - to unintentionally provide insufficient information when - requesting support. Previously it wasn't obvious that the - information we need in bug reports is usually also required in - support requests.
-Removed documentation about packages that haven't been - provided in years.
-Privoxy-Regression-Test:
- -Only log the test number when not running in verbose mode The - position of the test is rarely relevant and it previously wasn't - exactly obvious which one of the numbers was useful to repeat the - test with --test-number.
-GNUmakefile improvements:
- -Factor generate-config-file out of config-file to make testing - more convenient.
+Adjust build_request_line() to create a CONNECT request line when https-inspecting and forwarding to a + HTTP proxy. Fixes SF bug #925 reported by Wen Yue.
The clean target now also takes care of patch leftovers.
+load_config(): Add a space that was missing in a log message.
Privoxy 3.0.20 beta contained the - following changes compared to the previous stable release:
- -Bug fixes:
- +General improvements:
Client sockets are now properly shutdown and drained before - being closed. This fixes page truncation issues with clients that - aggressively pipeline data on platforms that otherwise discard - already written data. The issue mainly affected Opera users and - was initially reported by Kevin in #3464439, szotsaki provided - additional information to track down the cause.
+serve(): Close the client socket as well if the server socket for an inspected connection has been + closed. Privoxy currently can't establish a new server connection when the client socket is reused and + would drop the connection in continue_https_chat() anyway.
Fix latency calculation for shared connections (disabled by - default). It was broken since their introduction in 2009. The - calculated latency for most connections would be 0 in which case - the timeout detection failed to account for the real latency.
+Don't disable redirect checkers in redirect_url() Disable them in handle_established_connection() + instead. Doing it in redirect_url() prevented the +redirect{} and +fast-redirects{} actions from being + logged with LOG_LEVEL_ACTIONS.
Reject URLs with invalid port. Previously they were parsed - incorrectly and characters between the port number and the first - slash were silently dropped as shown by curl test 187.
+handle_established_connection(): Slightly improve a comment
The default-server-timeout and socket-timeout directives - accept 0 as valid value.
+handle_established_connection(): Fix a comment
Fix a race condition on Windows that could cause Privoxy to - become unresponsive after toggling it on or off through the - taskbar icon. Reported by Tim H. in #3525694.
+socks5_connect(): Fix indentation.
Fix the compilation on Windows when configured without IPv6 - support.
-Fix an assertion that could cause debug builds to abort() in - case of socks5 connection failures with "debug 2" enabled.
-Fix an assertion that could cause debug builds to abort() if a - filter contained nul bytes in the replacement text.
-General improvements:
- -Significantly improved keep-alive support for both client and - server connections.
+handle_established_connection(): Improve an error message
New debug log level 65536 which logs all actions that were - applied to the request.
+create_pattern_spec(): Fix ifdef indentation
New directive client-header-order to forward client headers in - a different order than the one in which they arrived.
+Fix comment typos
New directive tolerate-pipelining to allow client-side - pipelining. If enabled (3.0.20 beta enables it by default), - Privoxy will keep pipelined client requests around to deal with - them once the current request has been served.
+Add a CGI handler for /wpad.dat that returns a Proxy Auto-Configuration (PAC) file. Among other things, + it can be used to instruct clients through DHCP to use Privoxy as proxy. For example with the dnsmasq + option: dhcp-option=252,http://config.privoxy.org/wpad.dat Initial patch by Richard Schneidt.
New --config-test option to let Privoxy exit after checking - whether or not the configuration seems valid. The limitations - noted in TODO #22 and #23 still apply. Based on a patch by - Ramkumar Chinchani.
+listen_loop(): When shutting down gracefully, close listening ports before waiting for the threads to + exit. Allows to start a second Privoxy with the same config file while the first Privoxy is still + running.
New limit-cookie-lifetime{} action to let cookies expire - before the end of the session. Suggested by Rick Sykes in - #1049575.
+Allow to edit the add-header action through the CGI editor by generalizing the code that got added with + the suppress-tag action. Closes SF patch request #146. Patch by Maxim Antonov.
Increase the hard-coded maximum number of actions and filter - files from 10 to 30 (each). It doesn't significantly affect - Privoxy's memory usage and recompiling wasn't an option for all - Privoxy users that reached the limit.
+process_encrypted_request(): Improve a log message The function only processes request headers and there + may still be unread request body data left to process.
Add support for chunk-encoded client request bodies. - Previously chunk-encoded request bodies weren't guaranteed to be - forwarded correctly, so this can also be considered a bug fix - although chunk-encoded request bodies aren't commonly used in the - real world.
+read_http_request_body(): Fix two error messages that used an incorrect variable.
Add support for Tor's optimistic-data SOCKS extension, which - can reduce the latency for requests on newly created connections. - Currently only the headers are sent optimistically and only if - the client request has already been read completely which rules - out requests with large bodies.
+chat(): Log the applied actions before deciding how to forward the request.
After preventing the client from pipelining, don't signal - keep-alive intentions. When looking at the response headers - alone, it previously wasn't obvious from the client's perspective - that no additional responses should be expected.
+parse_time_header(): Silence a coverity complaint when building without assertions.
Stop considering client sockets tainted after receiving a - request with body. It hasn't been necessary for a while now and - unnecessarily causes test failures when using curl's test - suite.
+receive_encrypted_request_headers(): Improve a log message
Allow HTTP/1.0 clients to signal interest in keep-alive - through the Proxy-Connection header. While such client are rare - in the real world, it doesn't hurt and couple of curl tests rely - on it.
+mbedTLS get_ciphersuites_from_string(): Use strlcpy() instead of strncpy(). Previously the terminating + NUL wasn't copied which resulted in a compiler warning. This didn't cause actual problems as the target + buffer was initialized by zalloc_or_die() so the last byte of the target buffer was NUL already. Actually + copying the terminating NUL seems clearer, though.
Only remove duplicated Content-Type headers when filters are - enabled. If they are not it doesn't cause ill effects and the - user might not want it. Downgrade the removal message to - LOG_LEVEL_HEADER to clarify that it's not an error in Privoxy and - is unlikely to cause any problems in general. Anonymously - reported in #3599335.
+Remove compiler warnings. "log_error(LOG_LEVEL_FATAL, ..." doesn't return but apparently the compiler + doesn't know that. Get rid of several "this statement may fall through [-Wimplicit-fallthrough=]" + warnings.
Set the socket option SO_LINGER for the client socket.
+If the the response is chunk-encoded, ignore the Content-Length header sent by the server. Allows to + load https://redmine.lighttpd.net/ with filtering enabled.
Move several variable declarations to the beginning of their - code block. It's required when compiling with gcc 2.95 which is - still used on some platforms. Initial patch submitted by Simon - South in #3564815.
+Store the PEM certificate in a dynamically allocated buffer when https-inspecting. Should prevent errors + like: 2021-03-16 22:36:19.148 7f47bbfff700 Error: X509 PEM cert len 16694 is larger than buffer len 16383 + As a bonus it should slightly reduce the memory usage as most certificates are smaller than the previously + used fixed buffer. Reported by: Wen Yue
Optionally try to sanity-check strptime() results before - trusting them. Broken strptime() implementations have caused - problems in the past and the most recent offender seems to be - FreeBSD's libc (standards/173421).
+Don't log the applied actions in process_encrypted_request() Log them in continue_https_chat() instead + to mirror chat(). Prevents the applied actions from getting logged twice for the first request on an + https-inspected connection.
When filtering is enabled, let Range headers pass if the range - starts at the beginning. This should work around (or at least - reduce) the video playback issues with various Apple clients as - reported by Duc in #3426305.
+OpenSSL generate_host_certificate(): Use config.privoxy.org as Common Name Org and Org Unit if the real + host name is too long to get accepted by OpenSSL. Clients should only care about the Subject Alternative + Name anyway and we can continue to use the real host name for it. Reported by Miles Wen on + privoxy-users@.
Do not confuse a client hanging up with a connection time out. - If a client closes its side of the connection without sending a - request line, do not send the CLIENT_CONNECTION_TIMEOUT_RESPONSE, - but report the condition properly.
+OpenSSL generate_host_certificate(): Fix two error messsages.
Allow closing curly braces as part of action values as long as - they are escaped.
+Improve description of handle_established_connection()
On Windows, the logfile is now written before showing the GUI - error message which blocks until the user acknowledges it. - Reported by Adriaan in #3593603.
+OpenSSL ssl_store_cert(): Translate EVP_PKEY_EC to a string.
Remove an unreasonable parameter limit in the CGI interface. - The new parameter limit depends on the memory available and is - currently unlikely to be reachable, due to other limits in both - Privoxy and common clients. Reported by Andrew on - ijbswa-users@.
+OpenSSL ssl_store_cert(): Remove pointless variable initialization.
Decrease the chances of parse failures after requests with - unsupported methods were sent to the CGI interface.
+OpenSSL ssl_store_cert(): Initialize pointer with NULL instead of 0.
Action file improvements:
-Remove the comment that indicated that updated default.action - versions are released on their own.
-Block 'optimize.indieclick.com/' and - 'optimized-by.rubiconproject.com/'
-Unblock 'adjamblog.wordpress.com/' and - 'adjamblog.files.wordpress.com/'. Reported by Ryan Farmer in - #3496116.
-Unblock '/.*Bugtracker'. Reported by pwhk in #3522341.
-Add test URLs for '.freebsd.org' and '.watson.org'.
-Unblock '.urbandictionary.com/popular'.
-Block '.adnxs.com/'.
-Block 'farm.plista.com/widgetdata.php'.
-Block 'rotation.linuxnewmedia.com/'.
-Block 'reklamy.sfd.pl/'. Reported by kacperdominik in - #3399948.
-Block 'g.adspeed.net/'.
-Unblock 'websupport.wdc.com/'. Reported by Adam Piggot in - #3577851.
-Block '/openx/www/delivery/'.
-Disable fast-redirects for '.googleapis.com/'.
-Block 'imp.double.net/'. Reported by David Bo in #3070411.
-Block 'gm-link.com/' which is used for email tracking. - Reported by David Bo in #1812733.
-Verify that requests to "bwp." are blocked. URL taken from - #1736879 submitted by Francois Marier.
-Block '/.*bannerid='. Reported by Adam Piggott in - #2975779.
-Block 'cltomedia.info/delivery/' and '.adexprt.com/'. - Anonymously reported in #2965254.
+Disable fast-redirects for .microsoftonline.com/.
Block 'de17a.com/'. Reported by David Bo in #3061472.
+Disable fast-redirects for idp.springer.com/.
Block 'oskar.tradera.com/'. Reported by David Bo in - #3060596.
+Disable fast-redirects for .zeit.de/zustimmung
Block '/scripts/webtrends\.js'. Reported by johnd16 in - #3002729.
+Unblock adv-archiv.dfn-cert.de/
Block requests for 'pool.*.adhese.com/'. Reported by johnd16 - in #3002716.
+Block requests to eu-tlp01.kameleoon.eu/
Update path pattern for Coremetrics and add tests. Pattern and - URLs submitted by Adam Piggott #3168443.
+Block requests to fpa-events.arstechnica.com/
Enable +fast-redirects{check-decoded-url} for 'tr.anp.se/'. - Reported by David Bo in #3268832.
+Unblock nlnet.nl/.
Unblock '.conrad.se/newsletter/banners/'. Reported by David Bo - in #3413824.
-Block '.tynt.com/'. Reported by Dan Stahlke in #3421767.
-Unblock '.bbci.co.uk/radio/'. Reported by Adam Piggott in - #3569603.
-Block requests to 'service.maxymiser.net/'. Reported by - johnd16 in #3118401 (with a previous URL).
-Disable fast-redirects for Google's "let's pretend your - computer is infected" page.
-Unblock '/.*download' to resolve actionsfile feedback - #3498129. Submitted by Steven Kolins (soundcloud.com not - working).
-Unblock '.wlxrs.com/' which is required by hotmail.com. Fixes - #3413827 submitted by David Bo.
-Add two unblock patterns for popup radio and TV players. - Submitted by Adam Piggott in #3596089.
+Unblock adguard.com/.
Filter file improvements & bug fixes:
- -Add a referer tagger.
-Reduce the likelihood that the google filter messes up - HTML-generating JavaScript. Reported by Zeno Kugy in - #3520260.
-Documentation improvements:
- +Privoxy-Log-Parser:
Revised all OS X sections due to new packaging module - (OSXPackageBuilder).
+Highlight 'Socket timeout 3 reached: http://127.0.0.1:20000/no-filter/chunked-content/36'
Update the list of supported operating systems to clarify that - all Windows versions after 95 are expected to work and note that - the platform-specific code for AmigaOS and QNX currently isn't - maintained.
+Improve documentation for inactivity-detection mode
Update 'Signals' section, the only explicitly handled signals - are SIGINT, SIGTERM and SIGHUP.
+Detect date changes when looking for inactivity
Add Haiku to the list of operating systems on which Privoxy is - known to run.
+Add a --passed-request-statistics-threshold option That can be set to get statistics for requests that + were passed.
Add DragonFly to the list of BSDs on which Privoxy is known to - run.
+Add a "inactivity detection" mode Which can be useful for debugging purposes.
Removed references to redhat-specific documentation set since - it no longer exists.
+Bump version to 0.9.4
Removed references to building PDFs since we no longer do - so.
+Only run print_intro() and print_outro() when syntax highlighting
Multiple listen-address directives are supported since 3.0.18, - correct the documentation to say so.
+Rephrase a sentence in the documentation
Remove bogus section about long and short being preferable to - int.
+Highlight 'Client socket 7 is no longer usable. The server socket has been closed.'
Corrected some Internet JunkBuster references to Privoxy.
+Clarify --statistics output by explicitly mentioning that the status codes sent by the server may differ + from the ones in "debug 512" messages.
Removed references to www.junkbusters.com since it is no - longer maintained. Reported by Angelina Matson.
+Fix typo in the --statistics output
Various grammar and spelling corrections
+Remove an unused variable
Add a client-header-tagger{} example for disabling filtering - for range requests.
-Correct a URL in the "Privoxy with Tor" FAQ.
-Spell 'refresh-tags' correctly. Reported by Don in - #3571927.
-Sort manpage options alphabetically.
-Remove an incorrect sentence in the toggle section. The toggle - state doesn't affect whether or not the Windows version uses the - tray icon. Reported by Zeno Kugy in #3596395.
-Add new contributors since 3.0.19.
+Highlight 'The peer notified us that the connection on socket 11 is going to be closed'
Log message improvements:
- +Privoxy-Regression-Test:
When stopping to watch a client socket due to pipelining, - additionally log the socket number.
-Log the client socket and its condition before closing it. - This makes it more obvious that the socket actually gets closed - and should help when diagnosing problems like #3464439.
-In case of SOCKS5 failures, do not explicitly log the server's - response. It hasn't helped so far and the response can already be - logged by enabling "debug 32768" anyway. This reverts v1.81 and - the follow-up bug fix v1.84.
-Relocate the connection-accepted message from listen_loop() to - serve(). This way it's printed by the thread that is actually - serving the connection which is nice when grepping for thread ids - in log files.
+Remove duplicated word in a comment.
Code cleanups:
- +regression-tests.action:
Remove compatibility layer for versions prior to 3.0 since it - has been obsolete for more than 10 years now.
-Remove the ijb_isupper() and ijb_tolower() macros from - parsers.c since they aren't used in this file.
-Removed the 'Functions declared include:' comment sections - since they tend to be incomplete, incorrect and out of date and - the benefit seems questionable.
-Various comment grammar and comprehensibility - improvements.
-Remove a pointless fflush() call in chat(). Flushing all - streams pretty much all the time for no obvious reason is - ridiculous.
-Relocate ijb_isupper()'s definition to project.h and get the - ijb_tolower() definition from there, too.
-Relocate ijb_isdigit()'s definition to project.h.
-Rename ijb_foo macros to privoxy_foo.
-Add malloc_or_die() which will allow to simplify code paths - where malloc() failures don't need to be handled gracefully.
-Add strdup_or_die() which will allow to simplify code paths - where strdup() failures don't need to be handled gracefully.
-Replace strdup() calls with strdup_or_die() calls where it's - safe and simplifies the code.
-Fix white-space around parentheses.
-Add missing white-space behind if's and the following - parentheses.
+Add fetch test for http://p.p/wpad.dat.
Unwrap a memcpy() call in resolve_hostname_to_ip().
+Bump for-privoxy-version to 3.0.33 which introduced the wpad.dat support.
Declare pcrs_get_delimiter()'s delimiters[] static const.
+Add more tests for the '/send-banner' code.
Various optimisations to remove dead code and merge - inefficient code structures for improved clarity, performance or - code compactness.
+Add test for OVE-20210203-0001.
Various data type corrections.
+Add a test for CVE-2021-20217.
Change visibility of several code segments when compiling - without FEATURE_CONNECTION_KEEP_ALIVE enabled for clarity.
-In pcrs_get_delimiter(), do not use delimiters outside the - ASCII range. Fixes a clang complaint.
-Fix an error message in get_last_url() nobody is supposed to - see. Reported by Matthew Fischer in #3507301.
-Fix a typo in the no-zlib-support complaint. Patch submitted - by Matthew Fischer in #3507304.
-Shorten ssplit()'s prototype by removing the last two - arguments. We always want to skip empty fields and ignore leading - delimiters, so having parameters for this only complicates the - API.
-Use an enum for the type of the action value.
-Rename action_name's member takes_value to value_type as it - isn't used as boolean.
-Turn family mismatches in match_sockaddr() into fatal - errors.
-Let enlist_unique_header() verify that the caller didn't pass - a header containing either \r or \n.
-uagen:
+Change the hashes used in load_config() to unsigned int. - That's what hash_string() actually returns and using a - potentially larger type is at best useless.
+Bump generated Firefox version to 91 (ESR)
Use privoxy_tolower() instead of vanilla tolower() with manual - casting of the argument.
+Bump version to 1.2.3
Catch ssplit() failures in parse_cgi_parameters().
+Bump copyright
Privoxy-Regression-Test:
- +Build system:
Add an 'Overwrite condition' directive to skip any matching - tests before it. As it has a global scope, using it is more - convenient than clowning around with the Ignore directive.
+configure: Bump SOURCE_DATE_EPOCH.
Log to STDOUT instead of STDERR.
+GNUmakefile.in: Fix typo.
Include the Privoxy version in the output.
+configure: Add another warning in case --disable-pthread is used while POSIX threads are available. + Various features don't even compile when not using threads.
Various grammar and spelling corrections in documentation and - code.
+Add configure option to enable MemorySanitizer.
Additional tests for range requests with filtering - enabled.
+Add configure option to enable UndefinedBehaviorSanitizer.
Tests with mostly invalid range request.
+Add configure option to enable AddressSanitizer.
Add a couple of hide-if-modified-since{} tests with different - date formats.
+Bump copyright
Cleaned up the format of the regression-tests.action file to - match the format of default.action.
+Add a configure option to disable pcre JIT compilation. While JIT compilation makes filtering faster it + can cause false-positive valgrind complaints. As reported by Gwyn Ciesla in SF bug 924 it also can cause + problems when the SELinux policy does not grant Privoxy "execmem" privileges.
Remove the "Copyright" line from print_version(). When using - --help, every line of screen space matters and thus shouldn't be - wasted on things the user doesn't care about.
+configure: Remove obsolete RPM_BASE check
Privoxy-Log-Parser:
- +Windows build system:
Improve the --statistics performance by skipping sanity checks - for input that shouldn't affect the results anyway. Add a - --strict-checks option that enables some of the checks again, - just in case anybody cares.
+Update the build script to use mbed tls version 2.6.11.
The distribution of client requests per connection is included - in the --statistic output.
+Update build script to use the final 8.45 pcre library.
The --accept-unknown-messages option has been removed and the - behavior is now the default.
-Accept and (mostly) highlight new log messages introduced with - Privoxy 3.0.20.
-uagen:
- -Bump generated Firefox version to 17.
+Put all the '--enable-xxx' options in the configure call together.
GNUmakefile improvements:
- +Documentation:
The dok-tidy target no longer taints documents with a - tidy-mark
+contacting: Remove obsolete reference to announce.sgml.
Change RA_MODE from 0664 to 0644. Suggested by Markus Dittrich - in #3505445.
+contacting: Request that the browser cache is cleared before producing a log file for submission.
Remove tidy's clean flag as it changes the scope of - attributes. Link-specific colors end up being applied to all - text. Reported by Adam Piggott in #3569551.
+Sponsor FAQ: Note that Privoxy users may follow sponsor links without Referer header set.
Leave it up to the user whether or not smart tags are - inserted.
+newfeatures: Clarify that https inspection also allows to filter https responses.
Let w3m itself do the line wrapping for the config file. It - works better than fmt as it can honour pre tags causing less - unintentional line breaks.
+developer-manual: Mention that announce.txt should be updated when doing a release.
Ditch a pointless '-r' passed to rm to delete files.
+config: Explicitly mention that the CGI pages disclosing the ca-password can be blocked and upgrade the + disclosure paragraphs to a warning.
The config-file target now requires less manual intervention - and updates the original config.
+Put all the requested debug options in the config file. Section 11.1 of the Privoxy user manual lists + all the debug options that should be enabled when reporting problems or requesting support. Make it easier + for users to do the right thing by having all those options present in the config.
Change WDUMP to generate ASCII. Add WDUMP_UTF8 to allow UTF-8 - in the AUTHORS file so the names are right.
+Update TODO list item #184 to note that WolfSSL support will (hopefully) appear after the 3.0.34 + release
Stop pretending that lynx and links are supported for the - documentation.
+Update max-client-connections's description. On modern systems other than Windows Privoxy should use + poll() in which case the FD_SETSIZE value isn't releveant.
configure improvements:
- -On Haiku, do not pass -lpthread to the compiler. Haiku's - pthreads implementation is contained in its system library, - libroot, so no additional library needs to be searched. Patch - submitted by Simon South in #3564815.
+Add a warning that the socket-timeout does not apply to operations done by TLS libraries
Additional Haiku-specific improvements. Disable checks - intended for multi-user systems as Haiku is presently - single-user. Group Haiku-specific settings in their own section, - following the pattern for Solaris, OS/2 and AmigaOS. Add - additional library-related settings to remove the need for - providing configure with custom LDFLAGS. Submitted by Simon South - in #3574538.
+Make documentation slightly less "offensive" for some people by avoiding the word "hell".
A quick list of things to be aware of before upgrading from earlier - versions of Privoxy:
- +A quick list of things to be aware of before upgrading from earlier versions of Privoxy:
The recommended way to upgrade Privoxy is to backup your old configuration - files, install the new ones, verify that Privoxy is working correctly and finally merge - back your changes using diff and - maybe patch.
- -There are a number of new features in each Privoxy release and most of them have to be - explicitly enabled in the configuration files. Old configuration - files obviously don't do that and due to syntax changes using old - configuration files with a new The recommended way to upgrade Privoxy is to backup your old + configuration files, install the new ones, verify that Privoxy is working + correctly and finally merge back your changes using diff and maybe + patch.
+There are a number of new features in each Privoxy release and most of + them have to be explicitly enabled in the configuration files. Old configuration files obviously don't do + that and due to syntax changes using old configuration files with a new Privoxy isn't always possible anyway.
Note that some installers remove earlier versions completely, - including configuration files, therefore you should really save any - important configuration files!
+Note that some installers remove earlier versions completely, including configuration files, therefore you + should really save any important configuration files!
On the other hand, other installers don't overwrite existing - configuration files, thinking you will want to do that - yourself.
+On the other hand, other installers don't overwrite existing configuration files, thinking you will want + to do that yourself.
In the default configuration only fatal errors are logged now. - You can change that in the debug - section of the configuration file. You may also want to enable - more verbose logging until you verified that the new Privoxy version is working as expected.
+In the default configuration only fatal errors are logged now. You can change that in the debug section of the configuration file. You may also want to enable more verbose + logging until you verified that the new Privoxy version is working as + expected.
Three other config file settings are now off by default: - enable-remote-toggle, - enable-remote-http-toggle, - and enable-edit-actions. If you - use or want these, you will need to explicitly enable them, and be - aware of the security issues involved.
+Three other config file settings are now off by default: enable-remote-toggle, enable-remote-http-toggle, and enable-edit-actions. If you use or want these, you will need to + explicitly enable them, and be aware of the security issues involved.