From 5ffca8e39df2da75bcc3458307c25893a47fdf16 Mon Sep 17 00:00:00 2001 From: Fabian Keil Date: Sun, 5 Aug 2007 15:19:50 +0000 Subject: [PATCH] - Don't claim HTTP/1.1 compliance. - Use $ in some of the path pattern examples. - Use a hide-user-agent example argument without leading and trailing space. - Make it clear that the cookie actions work with HTTP cookies only. - Rephrase the inspect-jpegs text to underline that it's only meant to protect against a single exploit. --- doc/source/user-manual.sgml | 79 ++++++++++++++++++++++--------------- 1 file changed, 47 insertions(+), 32 deletions(-) diff --git a/doc/source/user-manual.sgml b/doc/source/user-manual.sgml index 173f56af..9f7a8a22 100644 --- a/doc/source/user-manual.sgml +++ b/doc/source/user-manual.sgml @@ -33,7 +33,7 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: user-manual.sgml,v 2.32 2007/06/07 12:36:22 fabiankeil Exp $ + $Id: user-manual.sgml,v 2.33 2007/07/27 10:57:35 hal9 Exp $ Copyright (C) 2001-2007 Privoxy Developers http://www.privoxy.org/ See LICENSE. @@ -59,7 +59,7 @@ -$Id: user-manual.sgml,v 2.32 2007/06/07 12:36:22 fabiankeil Exp $ +$Id: user-manual.sgml,v 2.33 2007/07/27 10:57:35 hal9 Exp $ - content-type-overwrite @@ -3208,12 +3215,12 @@ new action It is also useful to make sure the header isn't used as a cookie - replacement. + replacement (unlikely but possible). Blocking the If-None-Match: header shouldn't cause any caching problems, as long as the If-Modified-Since: header - isn't blocked as well. + isn't blocked or missing as well. It is recommended to use this action together with @@ -3284,10 +3291,10 @@ new action Notes: - This action is only concerned with incoming cookies. For - outgoing cookies, use + This action is only concerned with incoming HTTP cookies. For + outgoing HTTP cookies, use crunch-outgoing-cookies. - Use both to disable cookies completely. + Use both to disable HTTP cookies completely. It makes no sense at all to use this action in conjunction @@ -3400,7 +3407,7 @@ new action Typical use: - Prevent the web server from reading any cookies from your system + Prevent the web server from reading any HTTP cookies from your system @@ -3435,10 +3442,10 @@ new action Notes: - This action is only concerned with outgoing cookies. For - incoming cookies, use + This action is only concerned with outgoing HTTP cookies. For + incoming HTTP cookies, use crunch-incoming-cookies. - Use both to disable cookies completely. + Use both to disable HTTP cookies completely. It makes no sense at all to use this action in conjunction @@ -3574,8 +3581,8 @@ new action This is a left-over from the time when Privoxy didn't support important HTTP/1.1 features well. It is left here for the unlikely case that you experience HTTP/1.1 related problems with some server - out there. Not all (optional) HTTP/1.1 features are supported yet, so there - is a chance you might need this action. + out there. Not all HTTP/1.1 features and requirements are supported yet, + so there is a chance you might need this action. @@ -4077,17 +4084,17 @@ new action - forward-socks4a 127.0.0.1:9050 . to use the socks4a proxy listening at 127.0.0.1 port 9050. - Replace forward-socks4a with forward-socks4 to use a socks4 connection (with local DNS - resolution) instead. + forward-socks4a 127.0.0.1:9050 . to use the socks4a proxy listening at + 127.0.0.1 port 9050. Replace forward-socks4a with forward-socks4 + to use a socks4 connection (with local DNS resolution) instead. forward-socks4a 127.0.0.1:9050 proxy.example.org:8000 to use the socks4a proxy listening at 127.0.0.1 port 9050 to reach the HTTP proxy listening at proxy.example.org port 8000. - Replace forward-socks4a with forward-socks4 to use a socks4 connection (with local DNS - resolution) instead. + Replace forward-socks4a with forward-socks4 to use a socks4 connection + (with local DNS resolution) instead. @@ -4137,7 +4144,7 @@ new action -hide-if-modified-since \ -overwrite-last-modified \ } -TAG:^User-Agent: fetch libfetch/2.0$ +TAG:^User-Agent: fetch libfetch/2\.0$ @@ -4952,7 +4959,12 @@ new action allow execution of code on the target system, giving an attacker access to the system in question by merely planting an altered JPEG image, which would have no obvious indications of what lurks inside. This action - prevents unwanted intrusion. + prevents this exploit. + + + Note that the described exploit is only one of many, + using this action does not mean that you no longer + have to patch the client. @@ -8932,6 +8944,9 @@ In file: user.action [ View ] [ Edit ]