| Privoxy 3.0.19 User Manual | +Privoxy 3.0.33 User Manual | ||||
|---|---|---|---|---|---|
| Prev | - +Prev | - - | Next | +Next | |
Privoxy 3.0.19 is a stable release. - The changes since 3.0.18 stable 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:
- +Security/Reliability:
Prevent a segmentation fault when de-chunking buffered - content. It could be triggered by malicious web servers if - Privoxy was configured to filter the content and running on a - platform where SIZE_T_MAX isn't larger than UINT_MAX, which - probably includes most 32-bit systems. On those platforms, all - Privoxy versions before 3.0.19 appear to be affected. To be on - the safe side, this bug should be presumed to allow code - execution as proving that it doesn't seems unrealistic.
-Do not expect a response from the SOCKS4/4A server until it - got something to respond to. This regression was introduced in - 3.0.18 and prevented the SOCKS4/4A negotiation from working. - Reported by qqqqqw in #3459781.
+cgi_error_no_template(): Encode the template name to prevent XSS (cross-side scripting) when Privoxy is + configured to servce the user-manual itself. Commit 0e668e9409c. OVE-20211102-0001. CVE-2021-44543. + Reported by: Artem Ivanov
General improvements:
- -Fix an off-by-one in an error message about connect - failures.
+get_url_spec_param(): Free memory of compiled pattern spec before bailing. Reported by Joshua Rogers + (Opera) who also provided the fix. Commit 652b4b7cb0. OVE-20211201-0003. CVE-2021-44540.
Use a GNUMakefile variable for the webserver root directory - and update the path. Sourceforge changed it which broke various - web-related targets.
+process_encrypted_request_headers(): Free header memory when failing to get the request destination. + Reported by Joshua Rogers (Opera) who also provided the fix. Commit 0509c58045. OVE-20211201-0002. + CVE-2021-44541.
Update the CODE_STATUS description.
+send_http_request(): Prevent memory leaks when handling errors Reported by Joshua Rogers (Opera) who + also provided the fix. Commit c48d1d6d08. OVE-20211201-0001. CVE-2021-44542.
The following changes were made between 3.0.17 and 3.0.18:
- -Bug fixes:
-If a generated redirect URL contains characters RFC 3986 - doesn't permit, they are (re)encoded. Not doing this makes - Privoxy versions from 3.0.5 to 3.0.17 susceptible to HTTP - response splitting (CWE-113) attacks if the - +fast-redirects{check-decoded-url} action is used.
-Fix a logic bug that could cause Privoxy to reuse a server - socket after it got tainted by a server-header-tagger-induced - block that was triggered before the whole server response had - been read. If keep-alive was enabled and the request following - the blocked one was to the same host and using the same - forwarding settings, Privoxy would send it on the tainted server - socket. While the server would simply treat it as a pipelined - request, Privoxy would later on fail to properly parse the - server's response as it would try to parse the unread data from - the first response as server headers for the second one. - Regression introduced in 3.0.17.
-When implying keep-alive in client_connection(), remember that - the client didn't. Fixes a regression introduced in 3.0.13 that - would cause Privoxy to wait for additional client requests after - receiving a HTTP/1.1 request with "Connection: close" set and - connection sharing enabled. With clients which terminates the - client connection after detecting that the whole body has been - received it doesn't really matter, but with clients that don't - the connection would be kept open until it timed out.
-Fix a subtle race condition between - prepare_csp_for_next_request() and sweep(). A thread preparing - itself for the next client request could briefly appear to be - inactive. If all other threads were already using more recent - files, the thread could get its files swept away under its feet. - So far this has only been reproduced while stress testing in - valgrind while touching action files in a loop. It's unlikely to - have caused any actual problems in the real world.
-Disable filters if SDCH compression is used unless filtering - is forced. If SDCH was combined with a supported compression - algorithm, Privoxy previously could try to decompress it and - ditch the Content-Encoding header even though the SDCH - compression wasn't dealt with. Reported by zebul666 in - #3225863.
-Make a copy of the --user value and only mess with that when - splitting user and group. On some operating systems modifying the - value directly is reflected in the output of ps and friends and - can be misleading. Reported by zepard in #3292710.
+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.
If forwarded-connect-retries is set, only retry if Privoxy is - actually forwarding the request. Previously direct connections - would be retried as well.
+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.
Fixed a small memory leak when retrying connections with IPv6 - support enabled.
+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.
Remove an incorrect assertion in - compile_dynamic_pcrs_job_list() It could be triggered by a pcrs - job with an invalid pcre pattern (for example one that contains a - lone quantifier).
+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.
If the --user argument user[.group] contains a dot, always - bail out if no group has been specified. Previously the intended, - but undocumented (and apparently untested), behaviour was to try - interpreting the whole argument as user name, but the detection - was flawed and checked for '0' instead of '\0', thus merely - preventing group names beginning with a zero.
+load_config(): Add a space that was missing in a log message.
In html_code_map[], use a numeric character reference instead - of ' which wasn't standardized before XHTML 1.0.
+read_http_request_body(): Fix two error messages that used an incorrect variable.
Fix an invalid free when compiled with - FEATURE_GRACEFUL_TERMINATION and shut down through - http://config.privoxy.org/die
-In get_actions(), fix the "temporary" backwards compatibility - hack to accept block actions without reason. It also covered - other actions that should be rejected as invalid. Reported by - Billy Crook.
+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.
General improvements:
-Privoxy can (re)compress buffered content before delivering it - to the client. Disabled by default as most users wouldn't benefit - from it.
-The +fast-redirects{check-decoded-url} action checks URL - segments separately. If there are other parameters behind the - redirect URL, this makes it unnecessary to cut them off by - additionally using a +redirect{} pcrs command. Initial patch - submitted by Jamie Zawinski in #3429848.
-When loading action sections, verify that the referenced - filters exist. Currently missing filters only result in an error - message, but eventually the severity will be upgraded to - fatal.
-Allow to bind to multiple separate addresses. Patch set - submitted by Petr Pisar in #3354485.
-Set socket_error to errno if connecting fails in - rfc2553_connect_to(). Previously rejected direct connections - could be incorrectly reported as DNS issues if Privoxy was - compiled with IPv6 support.
-Adjust url_code_map[] so spaces are replaced with %20 instead - of '+' While '+' can be used by client's submitting form data, - this is not actually what Privoxy is using the lookups for. This - is more of a cosmetic issue and doesn't fix any known - problems.
-When compiled without FEATURE_FAST_REDIRECTS, do not silently - ignore +fast-redirect{} directives
-Added a workaround for GNU libc's strptime() reporting - negative year values when the parsed year is only specified with - two digits. On affected systems cookies with such a date would - not be turned into session cookies by the +session-cookies-only - action. Reported by Vaeinoe in #3403560
-Fixed bind failures with certain GNU libc versions if no - non-loopback IP address has been configured on the system. This - is mainly an issue if the system is using DHCP and Privoxy is - started before the network is completely configured. Reported by - Raphael Marichez in #3349356. Additional insight from Petr - Pisar.
-Privoxy log messages now use the ISO 8601 date format - %Y-%m-%d. It's only slightly longer than the old format, but - contains the full date including the year and allows sorting by - date (when grepping in multiple log files) without hassle.
-In get_last_url(), do not bother trying to decode URLs that do - not contain at least one '%' sign. It reduces the log noise and a - number of unnecessary memory allocations.
-In case of SOCKS5 failures, dump the socks response in the log - message.
-Simplify the signal setup in main().
-Streamline socks5_connect() slightly.
-In socks5_connect(), require a complete socks response from - the server. Previously Privoxy didn't care how much data the - server response contained as long as the first two bytes - contained the expected values. While at it, shrink the buffer - size so Privoxy can't read more than a whole socks response.
-In chat(), do not bother to generate a client request in case - of direct CONNECT requests. It will not be used anyway.
-Reduce server_last_modified()'s stack size.
+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.
Shorten get_http_time() by using strftime().
+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.
Constify the known_http_methods pointers in - unknown_method().
+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.
Constify the time_formats pointers in parse_header_time().
+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@.
Constify the formerly_valid_actions pointers in - action_used_to_be_valid().
+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.
Introduce a GNUMakefile MAN_PAGE variable that defaults to - privoxy.1. The Debian package uses section 8 for the man page and - this should simplify the patch.
+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.
Deduplicate the INADDR_NONE definition for Solaris by moving - it to jbsockets.h
+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.
In block_url(), ditch the obsolete workaround for ancient - Netscape versions that supposedly couldn't properly deal with - status code 403.
+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.
Remove a useless NULL pointer check in load_trustfile().
+handle_established_connection(): Slightly improve a comment.
Remove two useless NULL pointer checks in - load_one_re_filterfile().
+handle_established_connection(): Fix a comment.
Change url_code_map[] from an array of pointers to an array of - arrays It removes an unnecessary layer of indirection and on - 64bit system reduces the size of the binary a bit.
+socks5_connect(): Fix indentation.
Fix various typos. Fixes taken from Debian's 29_typos.dpatch - by Roland Rosenfeld.
+handle_established_connection(): Improve an error message.
Add a dok-tidy GNUMakefile target to clean up the messy HTML - generated by the other dok targets.
+create_pattern_spec(): Fix ifdef indentation.
GNUisms in the GNUMakefile have been removed.
+Fix comment typos.
Change the HTTP version in static responses to 1.1
+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.
Synced config.sub and config.guess with upstream - 2011-11-11/386c7218162c145f5f9e1ff7f558a3fbb66c37c5.
+chat(): Log the applied actions before deciding how to forward the request.
Add a dedicated function to parse the values of toggles. - Reduces duplicated code in load_config() and provides better - error handling. Invalid or missing toggle values are now a fatal - error instead of being silently ignored.
+parse_time_header(): Silence a coverity complaint when building without assertions.
Terminate HTML lines in static error messages with \n instead - of \r\n.
+receive_encrypted_request_headers(): Improve a log message.
Simplify cgi_error_unknown() a bit.
+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.
In LogPutString(), don't bother looking at pszText when not - actually logging anything.
+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.
Change ssplit()'s fourth parameter from int to size_t. Fixes a - clang complaint.
+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
Add a warning that the statistics currently can't be trusted. - Mention Privoxy-Log-Parser's --statistics option as an - alternative for the time being.
+OpenSSL generate_host_certificate(): Fix two error messsages.
In rfc2553_connect_to(), start setting cgi->error_message - on error.
+Improve description of handle_established_connection()
Change the expected status code returned for http://p.p/die - depending on whether or not FEATURE_GRACEFUL_TERMINATION is - available.
+OpenSSL ssl_store_cert(): Translate EVP_PKEY_EC to a string.
In cgi_die(), mark the client connection for closing. If the - client will fetch the style sheet through another connection it - gets the main thread out of the accept() state and should thus - trigger the actual shutdown.
+OpenSSL ssl_store_cert(): Remove pointless variable initialization.
Add a proper CGI message for cgi_die().
+OpenSSL ssl_store_cert(): Initialize pointer with NULL instead of 0.
Don't enforce a logical line length limit in - read_config_line().
-Slightly refactor server_last_modified() to remove useless - gmtime*() calls.
-Action file improvements:
+In get_content_type(), also recognize '.jpeg' as JPEG - extension.
+Disable fast-redirects for .microsoftonline.com/.
Add '.png' to the list of recognized file extensions in - get_content_type().
+Disable fast-redirects for idp.springer.com/.
In block_url(), consistently use the block reason "Request - blocked by Privoxy" In two places the reason was "Request for - blocked URL" which hides the fact that the request got blocked by - Privoxy and isn't necessarily correct as the block may be due to - tags.
+Disable fast-redirects for .zeit.de/zustimmung.
In listen_loop(), reload the configuration files after - accepting a new connection instead of before. Previously the - first connection that arrived after a configuration change would - still be handled with the old configuration.
+Unblock adv-archiv.dfn-cert.de/.
In chat()'s receive-data loop, skip a client socket check if - the socket will be written to right away anyway. This can - increase the transfer speed for unfiltered content on fast - network connections.
+Block requests to eu-tlp01.kameleoon.eu/.
The socket timeout is used for SOCKS negotiations as well - which previously couldn't timeout.
+Block requests to fpa-events.arstechnica.com/.
Don't keep the client connection alive if any configuration - file changed since the time the connection came in. This is - closer to Privoxy's behaviour before keep-alive support for - client connection has been added and also less confusing in - general.
+Unblock nlnet.nl/.
Treat all Content-Type header values containing the pattern - 'script' as a sign of text. Reported by pribog in #3134970.
+Unblock adguard.com/.
Action file improvements:
- +Privoxy-Log-Parser:
Moved the site-specific block pattern section below the one - for the generic patterns so for requests that are matched in - both, the block reason for the domain is shown which is usually - more useful than showing the one for the generic pattern.
-Remove -prevent-compression from the fragile alias. It's no - longer used anywhere by default and isn't known to break stuff - anyway.
-Add a (disabled) section to block various Facebook tracking - URLs. Reported by Dan Stahlke in #3421764.
+Highlight 'Socket timeout 3 reached: http://127.0.0.1:20000/no-filter/chunked-content/36'.
Add a (disabled) section to rewrite and redirect - click-tracking URLs used on news.google.com. Reported by Dan - Stahlke in #3421755.
+Improve documentation for inactivity-detection mode.
Unblock linuxcounter.net/. Reported by Dan Stahlke in - #3422612.
+Detect date changes when looking for inactivity.
Block 'www91.intel.com/' which is used by Omniture. Reported - by Adam Piggott in #3167370.
+Add a --passed-request-statistics-threshold option that can be set to get statistics for requests that + were passed.
Disable the handle-as-empty-doc-returns-ok option and mark it - as deprecated. Reminded by tceverling in #2790091.
+Add a "inactivity detection" mode which can be useful for debugging purposes.
Add ".ivwbox.de/" to the "Cross-site user tracking" section. - Reported by Nettozahler in #3172525.
+Bump version to 0.9.4.
Unblock and fast-redirect ".awin1.com/.*=http://". Reported by - Adam Piggott in #3170921.
+Only run print_intro() and print_outro() when syntax highlighting.
Block "b.collective-media.net/".
+Rephrase a sentence in the documentation.
Widen the Debian popcon exception to "qa.debian.org/popcon". - Seen in Debian's 05_default_action.dpatch by Roland - Rosenfeld.
+Highlight 'Client socket 7 is no longer usable. The server socket has been closed.'.
Block ".gemius.pl/" which only seems to be used for user - tracking. Reported by johnd16 in #3002731. Additional input from - Lee and movax.
+Clarify --statistics output by explicitly mentioning that the status codes sent by the server may differ + from the ones in "debug 512" messages.
Disable banners-by-size filters for '.thinkgeek.com/'. The - filter only seems to catch pictures of the inventory.
+Fix typo in the --statistics output.
Block requests for 'go.idmnet.bbelements.com/please/showit/'. - Reported by kacperdominik in #3372959.
+Remove an unused variable.
Unblock adainitiative.org/.
-Add a fast-redirects exception for - '.googleusercontent.com/.*=cache'.
-Add a fast-redirects exception for - webcache.googleusercontent.com/.
-Unblock http://adassier.wordpress.com/ and - http://adassier.files.wordpress.com/.
+Highlight 'The peer notified us that the connection on socket 11 is going to be closed'.
Filter file improvements:
- +Privoxy-Regression-Test:
Let the yahoo filter hide '.ads'.
-Let the msn filter hide overlay ads for Facebook 'likes' in - search results and elements with the id 's_notf_div'. They only - seem to be used to advertise site 'enhancements'.
-Let the js-events filter additionally disarm setInterval(). - Suggested by dg1727 in #3423775.
+Remove duplicated word in a comment.
Documentation improvements:
- +regression-tests.action:
Clarify the effect of compiling Privoxy with zlib support. - Suggested by dg1727 in #3423782.
+Add fetch test for http://p.p/wpad.dat.
Point out that the SourceForge messaging system works like a - black hole and should thus not be used to contact individual - developers.
+Bump for-privoxy-version to 3.0.33 which introduced the wpad.dat support.
Mention some of the problems one can experience when not - explicitly configuring an IP addresses as listen address.
+Add more tests for the '/send-banner' code.
Explicitly mention that hostnames can be used instead of IP - addresses for the listen-address, that only the first address - returned will be used and what happens if the address is invalid. - Requested by Calestyo in #3302213.
+Add test for OVE-20210203-0001.
+Add a test for CVE-2021-20217.
Log message improvements:
- +uagen:
If only the server connection is kept alive, do not pretend to - wait for a new client request.
-Remove a superfluous log message in forget_connection().
-In chat(), properly report missing server responses as such - instead of calling them empty.
-In forwarded_connect(), fix a log message nobody should ever - see.
-Fix a log message in socks5_connect(), a failed write - operation was logged as failed read operation.
-Let load_one_actions_file() properly complain about a missing - '{' at the beginning of the file. Simply stating that a line is - invalid isn't particularly helpful.
+Bump generated Firefox version to 91 (ESR).
Do not claim to listen on a socket until Privoxy actually - does. Patch submitted by Petr Pisar #3354485
+Bump version to 1.2.3.
Prevent a duplicated LOG_LEVEL_CLF message when sending out - the "no-server-data" response.
+Bump copyright.
Also log the client socket when dropping a connection.
-Include the destination host in the 'Request ... marked for - blocking. limit-connect{...} doesn't allow CONNECT ...' message - Patch submitted by Saperski in #3296250.
-Prevent a duplicated log message if none of the resolved IP - addresses were reachable.
-In connect_to(), do not pretend to retry if - forwarded-connect-retries is zero or unset.
-When a specified user or group can't be found, put the name in - single-quotes when logging it.
-In rfc2553_connect_to(), explain getnameinfo() errors - better.
-Remove a useless log message in chat().
-When retrying to connect, also log the maximum number of - connection attempts.
-Rephrase a log message in compile_dynamic_pcrs_job_list(). - Divide the error code and its meaning with a colon. Call the pcrs - job dynamic and not the filter. Filters may contain dynamic and - non-dynamic pcrs jobs at the same time. Only mention the name of - the filter or tagger, but don't claim it's a filter when it could - be a tagger.
-In a fatal error message in load_one_actions_file(), cover - both URL and TAG patterns.
-In pcrs_strerror(), properly report unknown positive error - code values as such. Previously they were handled like 0 (no - error).
-Build system:
+In compile_dynamic_pcrs_job_list(), also log the actual error - code as pcrs_strerror() doesn't handle all errors reported by - pcre.
+configure: Bump SOURCE_DATE_EPOCH.
Don't bother trying to continue chatting if the client didn't - ask for it. Reduces log noise a bit.
+GNUmakefile.in: Fix typo.
Make two fatal error message in load_one_actions_file() more - descriptive.
+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.
In cgi_send_user_manual(), log when rejecting a file name due - to '/' or '..'.
+Add configure option to enable MemorySanitizer.
In load_file(), log a message if opening a file failed. The - CGI error message alone isn't too helpful.
+Add configure option to enable UndefinedBehaviorSanitizer.
In connection_destination_matches(), improve two log messages - to help understand why the destinations don't match.
+Add configure option to enable AddressSanitizer.
Rephrase a log message in serve(). Client request arrival - should be differentiated from closed client connections now.
+Bump copyright.
In serve(), log if a client connection isn't reused due to a - configuration file change.
+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.
Let mark_server_socket_tainted() always mark the server socket - tainted, just don't talk about it in cases where it has no - effect. It doesn't change Privoxy's behaviour, but makes - understanding the log file easier.
+configure: Remove obsolete RPM_BASE check.
configure:
- +Windows build system:
Added a --disable-ipv6-support switch for platforms where - support is detected but doesn't actually work.
-Do not check for the existence of strerror() and memmove() - twice
-Remove a useless test for setpgrp(2). Privoxy doesn't need it - and it can cause problems when cross-compiling.
+Update the build script to use mbed tls version 2.6.11.
Rename the --disable-acl-files switch to - --disable-acl-support. Since about 2001, ACL directives are - specified in the standard config file.
+Update build script to use the final 8.45 pcre library.
Update the URL of the 'Removing outdated PCRE version after - the next stable release' posting. The old URL stopped working - after one of SF's recent site "optimizations". Reported by Han - Liu.
+Put all the '--enable-xxx' options in the configure call together.
Privoxy-Regression-Test:
- +macOS build system:
Added --shuffle-tests option to increase the chances of - detection race conditions.
-Added a --local-test-file option that allows to use - Privoxy-Regression-Test without Privoxy.
-Added tests for missing socks4 and socks4a forwarders.
-The --privoxy-address option now works with IPv6 addresses - containing brackets, too.
-Perform limited sanity checks for parameters that are supposed - to have numerical values.
-Added a --sleep-time option to specify a number of seconds to - sleep between tests, defaults to 0.
-Disable the range-requests tagger for tests that break if it's - enabled.
-Log messages use the ISO 8601 date format %Y-%m-%d.
-Fix spelling in two error messages.
-In the --help output, include a list of supported tests and - their default levels.
-Adjust the tests to properly deal with FEATURE_TOGGLE being - disabled.
+The OSXPackageBuilder repository has been updated and can be used to create macOS packages again.
Privoxy-Log-Parser:
- +Documentation:
Perform limited sanity checks for command line parameters that - are supposed to have numerical values.
+contacting: Remove obsolete reference to announce.sgml.
Implement a --unbreak-lines-only option to try to revert MUA - breakage.
+contacting: Request that the browser cache is cleared before producing a log file for submission.
Accept and highlight: Added header: Content-Encoding: - deflate
+Sponsor FAQ: Note that Privoxy users may follow sponsor links without Referer header set.
Accept and highlight: Compressed content from 29258 to 8630 - bytes.
+newfeatures: Clarify that https inspection also allows to filter https responses.
Accept and highlight: Client request arrived in time on socket - 21.
+developer-manual: Mention that announce.txt should be updated when doing a release.
Highlight: Didn't receive data in time: a.fsdn.com:443
+config: Explicitly mention that the CGI pages disclosing the ca-password can be blocked and upgrade the + disclosure paragraphs to a warning.
Accept log messages with ISO 8601 time stamps, too.
+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.
+Update TODO list item #184 to note that WolfSSL support will (hopefully) appear after the 3.0.34 + release.
uagen:
- -Bump generated Firefox version to 8.0.
+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.
Only randomize the release date if the new - --randomize-release-date option is enabled. Firefox versions - after 4 use a fixed date string without meaning.
+Add a warning that the socket-timeout does not apply to operations done by TLS libraries.
+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!
-On the other hand, other installers don't overwrite existing - configuration files, thinking you will want to do that - yourself.
+Note that some installers remove earlier versions completely, including configuration files, therefore you + should really save any important configuration files!
standard.action has been merged into - the default.action file.
+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.