You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
(30) |
Aug
(23) |
Sep
(7) |
Oct
(16) |
Nov
(10) |
Dec
(5) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(17) |
Feb
(17) |
Mar
(52) |
Apr
(10) |
May
(1) |
Jun
(4) |
Jul
(5) |
Aug
(81) |
Sep
(76) |
Oct
(32) |
Nov
(42) |
Dec
(72) |
2003 |
Jan
(65) |
Feb
(19) |
Mar
(45) |
Apr
(61) |
May
(123) |
Jun
(51) |
Jul
(69) |
Aug
(42) |
Sep
(19) |
Oct
(14) |
Nov
(25) |
Dec
(10) |
2004 |
Jan
(38) |
Feb
(49) |
Mar
(69) |
Apr
(39) |
May
(35) |
Jun
(43) |
Jul
(37) |
Aug
(50) |
Sep
(50) |
Oct
(61) |
Nov
(49) |
Dec
(55) |
2005 |
Jan
(73) |
Feb
(64) |
Mar
(53) |
Apr
(63) |
May
(32) |
Jun
(61) |
Jul
(56) |
Aug
(84) |
Sep
(47) |
Oct
(39) |
Nov
(39) |
Dec
(44) |
2006 |
Jan
(61) |
Feb
(62) |
Mar
(47) |
Apr
(51) |
May
(62) |
Jun
(46) |
Jul
(256) |
Aug
(326) |
Sep
(238) |
Oct
(192) |
Nov
(93) |
Dec
(73) |
2007 |
Jan
(55) |
Feb
(107) |
Mar
(60) |
Apr
(40) |
May
(72) |
Jun
(66) |
Jul
(48) |
Aug
(74) |
Sep
(87) |
Oct
(73) |
Nov
(41) |
Dec
(72) |
2008 |
Jan
(97) |
Feb
(89) |
Mar
(110) |
Apr
(131) |
May
(67) |
Jun
(51) |
Jul
(85) |
Aug
(39) |
Sep
(49) |
Oct
(33) |
Nov
(63) |
Dec
(71) |
2009 |
Jan
(60) |
Feb
(63) |
Mar
(67) |
Apr
(117) |
May
(76) |
Jun
(109) |
Jul
(82) |
Aug
(104) |
Sep
(123) |
Oct
(83) |
Nov
(51) |
Dec
(58) |
2010 |
Jan
(87) |
Feb
(88) |
Mar
(86) |
Apr
(87) |
May
(95) |
Jun
(51) |
Jul
(97) |
Aug
(69) |
Sep
(63) |
Oct
(62) |
Nov
(92) |
Dec
(42) |
2011 |
Jan
(43) |
Feb
(29) |
Mar
(55) |
Apr
(43) |
May
(60) |
Jun
(21) |
Jul
(44) |
Aug
(50) |
Sep
(22) |
Oct
(42) |
Nov
(29) |
Dec
(59) |
2012 |
Jan
(39) |
Feb
(31) |
Mar
(99) |
Apr
(51) |
May
(44) |
Jun
(29) |
Jul
(24) |
Aug
(21) |
Sep
(32) |
Oct
(46) |
Nov
(52) |
Dec
(68) |
2013 |
Jan
(25) |
Feb
(58) |
Mar
(105) |
Apr
(28) |
May
(47) |
Jun
(59) |
Jul
(45) |
Aug
(21) |
Sep
(26) |
Oct
(90) |
Nov
(48) |
Dec
(30) |
2014 |
Jan
(88) |
Feb
(10) |
Mar
(1) |
Apr
(14) |
May
(28) |
Jun
(7) |
Jul
(2) |
Aug
(10) |
Sep
(2) |
Oct
(11) |
Nov
(14) |
Dec
(12) |
2015 |
Jan
(10) |
Feb
(24) |
Mar
|
Apr
(35) |
May
(4) |
Jun
(15) |
Jul
(7) |
Aug
(10) |
Sep
(2) |
Oct
(33) |
Nov
(36) |
Dec
(19) |
2016 |
Jan
(10) |
Feb
(39) |
Mar
(24) |
Apr
(23) |
May
(20) |
Jun
(10) |
Jul
(2) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
(7) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Jean S. <je...@ea...> - 2017-02-25 18:14:59
|
Hi Lee, thanks for mentioning http://config.privoxy.org/show-url-info It indeed does show a very good explanation as for why my pattern wasn't blocked (it wasn't a host pattern per se): NOTE: This is a HTTPS URL, so the part after the "/" is ignored as Privoxy doesn't see the path for real HTTPS requests either. As pointed out kindly by Nick on the mailing list, the problem lied in my lack of understanding of how HTTPS works. The NOTE added by the http://config.privoxy.org/show-url-info is indeed a very explanatory sentence. I'd say that it wouldn't help to link FAQ 4.15 to HOST-PATTERN section for understanding (it would for the sake of convenience though). IMHO, you could add what you've added between parentheses to 4.15, it should be good enough. Maybe adding that NOTE explanation or part of it would make it even clearer. Best, Jean On 24/02/17 19:56, Lee wrote: > https://www.privoxy.org/faq/trouble.html#FLUSHIT > Try pasting the full URL of the offending ad into > http://config.privoxy.org/show-url-info > > which explains what the problem is. > > If we changed > The only exception to this is blocking by host patterns, > to > The only exception to this is blocking by host patterns (ie. > blocking on DNS name/IP address), > would that make it clearer? Or would making "host patterns" a link to > https://www.privoxy.org/user-manual/actions-file.html#HOST-PATTERN > be good enuf? > > The documentation does explain host & path patterns > https://www.privoxy.org/user-manual/actions-file.html#HOST-PATTERN > https://www.privoxy.org/user-manual/actions-file.html#PATH-PATTERN > but the FAQ could make it clearer that a host pattern matches just the > DNS name or IP address. > > Regards, > Lee > > > On 2/24/17, Jean Seurin <je...@ea...> wrote: >> Hi Ian, >> >> sorry for not being precise enough: I meant FAQ's 4.15 section: >> https://www.privoxy.org/faq/misc.html#SSL >> >> Excerpt: >> >> 4.15. How can Privoxy filter Secure (HTTPS) URLs? >> >> Since secure HTTP connections are encrypted SSL sessions between your >> browser and the secure site, and are meant to be reliably secure, there is >> little that Privoxy can do but hand the raw gibberish data though from one >> end to the other unprocessed. >> >> The only exception to this is blocking by host patterns, as the client needs >> to tell Privoxy the name of the remote server, so that Privoxy can establish >> the connection. If that name matches a host-only pattern, the connection >> will be blocked. >> >> Since we're not talking about content here, but really host pattern based, I >> think my case is part of the exception >> >> { +block{Nasty ads.} } >> .somesite.com/imp >> >> As for the email part, it doesn't matter: I'm talking about HTML email >> downloading ressources through the Privoxy proxy ( I mentioned emails >> because their HTML structure is different from DIV based pages, so it's a >> different pattern matching) >> >> I 'm anyway testing with a browser, and as said: >> http://test.somesite.com/imp is blocked but https://test.somesite.com/imp >> goes through. >> >> I'm really surprised that the host pattern doesn't match here, and I suspect >> it could be some config oddness on my part. >> >> I'd be happy with a confirmation that it should be working as expected (i.e. >> blocking by host pattern works also for https), just want to make sure the >> problem is on my side. >> >> Cheers, >> Jean >> >> On 22/02/17 14:49, Ian Silvester wrote: >>> Hi Jean, >>> >>> I'm afraid that no, Privoxy cannot filter HTTPS content. It is on the >>> TODO list, but may require funding to ever get done, and it is further >>> not clear how it could best be achieved whilst retaining the trust that >>> HTTPS connections afford. >>> >>> Could you provide a URL for the document section where you got the >>> impression that HTTPS is supported? I'm afraid I couldn't find section >>> 4.15 in current documentation. >>> >>> Email is sent over the SMTP protocol, so the only content Privoxy could >>> filter is that referenced via URLs in the messages (which is of course >>> very common). You could indeed write rules to handle that. >>> >>> Cheers, >>> >>> Ian >>> >>> My PGP public >>> key[http://diem.serveftp.net:8080/IanSilvesterPGPPublicKey.asc] >>> >>> On Tue, 21 Feb 2017, at 16:40, Jean Seurin wrote: >>>> Hi, >>>> >>>> I have this behaviour with a host pattern as follow (3.0.26): >>>> >>>> { +block{Nasty ads.} } >>>> .somesite.com/imp >>>> >>>> http://test.somesite.com/imp is blocked but >>>> https://test.somesite.com/imp goes through. >>>> >>>> My understanding was that host pattern would apply the block >>>> independently of the protocol (from the doc 4.15 section). >>>> >>>> Why isn't it blocking https? (My browsers and mail client are all using >>>> Privoxy proxy for both HTTP and HTTPS) >>>> >>>> As a fallback method, is there a possibility to filter content in email >>>> HTML (no div, only table tags) with a pattern? Like filter any <img> >>>> maybe ? >>>> >>>> Regards, >>>> Jean >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Check out the vibrant tech community on one of the world's most >>>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot >>>> _______________________________________________ >>>> Ijbswa-users mailing list >>>> Ijb...@li... >>>> https://lists.sourceforge.net/lists/listinfo/ijbswa-users >>> ------------------------------------------------------------------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> Ijbswa-users mailing list >>> Ijb...@li... >>> https://lists.sourceforge.net/lists/listinfo/ijbswa-users >> >> >> |
From: Jean S. <je...@ea...> - 2017-02-25 18:00:36
|
You massively made my day Nick. I've always assumed that the proxy my browser was communicating with could see what I could see in the URL box. Wrongly, https establish the TLS session with the domain first, then passes the request and it's parameters. So it's working as expected. Thanks! On 24/02/17 13:57, privoxyusers@i.lucanops.net wrote: > On Fri, 24 Feb 2017 13:44:15 +0100 > Jean Seurin <je...@ea...> wrote: >> The only exception to this is blocking by host patterns, as the >> client needs to tell Privoxy the name of the remote server, so that >> Privoxy can establish the connection. If that name matches a >> host-only pattern, the connection will be blocked. >> >> Since we're not talking about content here, but really host pattern >> based, I think my case is part of the exception { +block{Nasty ads.} } >> .somesite.com/imp > [...] >> I'm really surprised that the host pattern doesn't match here, and I >> suspect it could be some config oddness on my part. >> >> I'd be happy with a confirmation that it should be working as >> expected (i.e. blocking by host pattern works also for https), just >> want to make sure the problem is on my side. > That FAQ is perhaps not worded massively clearly. > > A host is just www.domain.com > A full URL would be https://www.domain.com/path/file.ext > > Privoxy can see what host, the computer on the internet, the > browser is asking for. It cannot see the rest of the URL, path/file.ext > in the above. That section is encrypted - like the rest of the content. > > So a filter picking out tracker.php to block > domain.com/malware/tracker.php would work on http, but not https. Block > domain.com and everything, no matter the protocol or path, will be > blocked. > > Nick > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Ijbswa-users mailing list > Ijb...@li... > https://lists.sourceforge.net/lists/listinfo/ijbswa-users |
From: privoxyusers@i.lucanops.net - 2017-02-25 00:58:41
|
On Fri, 24 Feb 2017 13:44:15 +0100 Jean Seurin <je...@ea...> wrote: > The only exception to this is blocking by host patterns, as the > client needs to tell Privoxy the name of the remote server, so that > Privoxy can establish the connection. If that name matches a > host-only pattern, the connection will be blocked. > > Since we're not talking about content here, but really host pattern > based, I think my case is part of the exception { +block{Nasty ads.} } > .somesite.com/imp [...] > > I'm really surprised that the host pattern doesn't match here, and I > suspect it could be some config oddness on my part. > > I'd be happy with a confirmation that it should be working as > expected (i.e. blocking by host pattern works also for https), just > want to make sure the problem is on my side. That FAQ is perhaps not worded massively clearly. A host is just www.domain.com A full URL would be https://www.domain.com/path/file.ext Privoxy can see what host, the computer on the internet, the browser is asking for. It cannot see the rest of the URL, path/file.ext in the above. That section is encrypted - like the rest of the content. So a filter picking out tracker.php to block domain.com/malware/tracker.php would work on http, but not https. Block domain.com and everything, no matter the protocol or path, will be blocked. Nick |
From: Lee <le...@gm...> - 2017-02-24 18:56:30
|
https://www.privoxy.org/faq/trouble.html#FLUSHIT Try pasting the full URL of the offending ad into http://config.privoxy.org/show-url-info which explains what the problem is. If we changed The only exception to this is blocking by host patterns, to The only exception to this is blocking by host patterns (ie. blocking on DNS name/IP address), would that make it clearer? Or would making "host patterns" a link to https://www.privoxy.org/user-manual/actions-file.html#HOST-PATTERN be good enuf? The documentation does explain host & path patterns https://www.privoxy.org/user-manual/actions-file.html#HOST-PATTERN https://www.privoxy.org/user-manual/actions-file.html#PATH-PATTERN but the FAQ could make it clearer that a host pattern matches just the DNS name or IP address. Regards, Lee On 2/24/17, Jean Seurin <je...@ea...> wrote: > Hi Ian, > > sorry for not being precise enough: I meant FAQ's 4.15 section: > https://www.privoxy.org/faq/misc.html#SSL > > Excerpt: > > 4.15. How can Privoxy filter Secure (HTTPS) URLs? > > Since secure HTTP connections are encrypted SSL sessions between your > browser and the secure site, and are meant to be reliably secure, there is > little that Privoxy can do but hand the raw gibberish data though from one > end to the other unprocessed. > > The only exception to this is blocking by host patterns, as the client needs > to tell Privoxy the name of the remote server, so that Privoxy can establish > the connection. If that name matches a host-only pattern, the connection > will be blocked. > > Since we're not talking about content here, but really host pattern based, I > think my case is part of the exception > > { +block{Nasty ads.} } > .somesite.com/imp > > As for the email part, it doesn't matter: I'm talking about HTML email > downloading ressources through the Privoxy proxy ( I mentioned emails > because their HTML structure is different from DIV based pages, so it's a > different pattern matching) > > I 'm anyway testing with a browser, and as said: > http://test.somesite.com/imp is blocked but https://test.somesite.com/imp > goes through. > > I'm really surprised that the host pattern doesn't match here, and I suspect > it could be some config oddness on my part. > > I'd be happy with a confirmation that it should be working as expected (i.e. > blocking by host pattern works also for https), just want to make sure the > problem is on my side. > > Cheers, > Jean > > On 22/02/17 14:49, Ian Silvester wrote: >> >> Hi Jean, >> >> I'm afraid that no, Privoxy cannot filter HTTPS content. It is on the >> TODO list, but may require funding to ever get done, and it is further >> not clear how it could best be achieved whilst retaining the trust that >> HTTPS connections afford. >> >> Could you provide a URL for the document section where you got the >> impression that HTTPS is supported? I'm afraid I couldn't find section >> 4.15 in current documentation. >> >> Email is sent over the SMTP protocol, so the only content Privoxy could >> filter is that referenced via URLs in the messages (which is of course >> very common). You could indeed write rules to handle that. >> >> Cheers, >> >> Ian >> >> My PGP public >> key[http://diem.serveftp.net:8080/IanSilvesterPGPPublicKey.asc] >> >> On Tue, 21 Feb 2017, at 16:40, Jean Seurin wrote: >>> >>> Hi, >>> >>> I have this behaviour with a host pattern as follow (3.0.26): >>> >>> { +block{Nasty ads.} } >>> .somesite.com/imp >>> >>> http://test.somesite.com/imp is blocked but >>> https://test.somesite.com/imp goes through. >>> >>> My understanding was that host pattern would apply the block >>> independently of the protocol (from the doc 4.15 section). >>> >>> Why isn't it blocking https? (My browsers and mail client are all using >>> Privoxy proxy for both HTTP and HTTPS) >>> >>> As a fallback method, is there a possibility to filter content in email >>> HTML (no div, only table tags) with a pattern? Like filter any <img> >>> maybe ? >>> >>> Regards, >>> Jean >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> Ijbswa-users mailing list >>> Ijb...@li... >>> https://lists.sourceforge.net/lists/listinfo/ijbswa-users >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, SlashDot.org! http://sdm.link/slashdot >> _______________________________________________ >> Ijbswa-users mailing list >> Ijb...@li... >> https://lists.sourceforge.net/lists/listinfo/ijbswa-users > > > > |
From: Ian S. <ian...@fa...> - 2017-02-22 13:49:56
|
Hi Jean, I'm afraid that no, Privoxy cannot filter HTTPS content. It is on the TODO list, but may require funding to ever get done, and it is further not clear how it could best be achieved whilst retaining the trust that HTTPS connections afford. Could you provide a URL for the document section where you got the impression that HTTPS is supported? I'm afraid I couldn't find section 4.15 in current documentation. Email is sent over the SMTP protocol, so the only content Privoxy could filter is that referenced via URLs in the messages (which is of course very common). You could indeed write rules to handle that. Cheers, Ian My PGP public key[http://diem.serveftp.net:8080/IanSilvesterPGPPublicKey.asc] On Tue, 21 Feb 2017, at 16:40, Jean Seurin wrote: > Hi, > > I have this behaviour with a host pattern as follow (3.0.26): > > { +block{Nasty ads.} } > .somesite.com/imp > > http://test.somesite.com/imp is blocked but > https://test.somesite.com/imp goes through. > > My understanding was that host pattern would apply the block > independently of the protocol (from the doc 4.15 section). > > Why isn't it blocking https? (My browsers and mail client are all using > Privoxy proxy for both HTTP and HTTPS) > > As a fallback method, is there a possibility to filter content in email > HTML (no div, only table tags) with a pattern? Like filter any <img> > maybe ? > > Regards, > Jean > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Ijbswa-users mailing list > Ijb...@li... > https://lists.sourceforge.net/lists/listinfo/ijbswa-users |
From: Jean S. <je...@ea...> - 2017-02-21 21:55:51
|
Hi, I have this behaviour with a host pattern as follow (3.0.26): { +block{Nasty ads.} } .somesite.com/imp http://test.somesite.com/imp is blocked but https://test.somesite.com/imp goes through. My understanding was that host pattern would apply the block independently of the protocol (from the doc 4.15 section). Why isn't it blocking https? (My browsers and mail client are all using Privoxy proxy for both HTTP and HTTPS) As a fallback method, is there a possibility to filter content in email HTML (no div, only table tags) with a pattern? Like filter any <img> maybe ? Regards, Jean |
From: Vanderdenduur <rv...@ic...> - 2016-08-31 18:05:09
|
Hello, > >From various post at https://www.prxbx.com/forums/ i see that you have developed some sort of https interface for privoxy and you're highly praised for this performance by some board users. The one behind ProxHTTPSProxyMII is whenever <https://www.prxbx.com/forums/showthread.php?tid=2172&pid=18822#pid18822> and indeed, thanks to him, his associates and testers, I only managed—with the help of cattleyavns <https://www.prxbx.com/forums/member.php?action=profile&uid=21948>—to run Privoxy along with ProxHTTPSProxyMII on OS X. As far as I’m aware, user cattleyavns is the first to set it up on OS X. I can only be “praised” for the tutorial I wrote for OS X users. Linux users have their threat here <https://www.prxbx.com/forums/showthread.php?tid=2228> and has been created by user kik0s. > >From your various post at https://www.prxbx.com/forums/ i can not find a single information - or maybe i overlooked it - what can be done with ProxHTTPSProxyMII. Info here <http://www.proxfilter.net/proxhttpsproxy/index.html> and there <https://www.prxbx.com/forums/forumdisplay.php?fid=48>. > You wrote this https://sourceforge.net/p/ijbswa/mailman/message/35070785/ and i quote from your post: > >> You may want to filter HTTPS requests as well… I know there have >> been pains and cries recently about Privoxy not being able to filter >> those requests. There is currently one working solution >> though—ProxHTTPSProxyMII >> <https://www.prxbx.com/forums/showthread.php?tid!91&pid728#pid18728>–that >> I use on a daily basis with virtually no hiccup at all. It works >> great and I confirm Privoxy is now able to block very nasty >> encrypted requests. > That says nothing to me. > > We (I !!) know more or less what can be done with Privoxy on the http side. Https traffic can only be blocked by domain names. Privoxy can't see the paths, nor the headers etc.. This kind of a simple domain blocking can also be done with uMask, dnsmasq or a hosts file. What can be done else or more with ProxHTTPSProxyMII? I should have mentioned that, thanks to ProxHTTPSProxyMII addon, Privoxy can now block any request based on the path side of the HTTPS URL. Example of useless request (still live): |https://s3.amazonaws.com/prod.obelusmedia/sdk/platforms/js/v2/sdk.min.js | * Privoxy alone; the only way to block it is to create the entry |.s3.amazonaws.com| in our blacklist. Not so great… Privoxy can not see that part: |/prod.obelusmedia/sdk/platforms/js/v2/sdk.min.js| * Privoxy + ProxHTTPSProxyMII; thus, a better solution is to block it using a rule set that detects “critical” keywords anywhere in the path (which would normally be invisible to Privoxy without the add-on) : |# Rejected Paths # # Ad Tech # /.*(chartbeat|cross.?sell|facebook|forester|mobiquo|sessioncam|yahoo) /.*(brightcove|googleads|obelusmedia|tag(commander|man)|xiti|zendesk) # <=== Match here! /.*(acymailing|bazaarvoice|boomr|cooladata|olark|omniture|trustpilot) /.*(blueconic|bluekai|breadcrumb|freshdesk|dmptag|usabilla|nugg\.?ad) /.*(adchemix|cedexis|segmentify|optincrusher|smartad|visual.?revenue) /.*(adrum|gigya|hapyak|konverto|krux|linkedin|openx|parsely|proximic) /.*(clickfunnel|disqus|google?.?(plus|service)|sonyoutube|optimizely) /.*(adsense|captify|le.?guide|mailchimp|recsys|ownedit|reevoo|runcpa) /.*(addthis|crazyegg|drupal|factortg|emsecure|hotjar|neewee|newgrove) /.*(dcstorm|marocrank|mediametrie|(socket|spoti)\.io|vicomi|volusion) /.*(adhese|adple?xme?d|dressipi|idcta|live.?intercept|newrelic|xsell) /.*(engageya|gemius|traff?ic.?trading|trading.?hub|xdirect|winnebago) /.*(awstats|iq.?digital|omnitag|pippity|pushwoosh|matchmedia|twitter) /.*(numbate|outbrain|pubn(ation|ub)|syntonic|web(perf|tre?k)|telerik) /.*(adestra|adriver|amshopby|dfp.?manager|kelkoo|shopify) /(.*[^a-z0-9])?basilic[^a-z0-9] | I created my own set of rules here <https://www.prxbx.com/forums/showthread.php?tid=2226&pid=18812#pid18812> ; I intend to update it soon with more efficient rules. The downside is that you need to create some exceptions if your favourite sites are broken. I usually use an “except” |.action| file—|PathExcepts.action|—called AFTER my |RejectedPath.action| file in Privoxy config. > Regards. > > |
From: Fabian K. <fk...@fa...> - 2016-08-29 11:12:29
|
Announcing Privoxy 3.0.26 stable -------------------------------------------------------------------- Privoxy 3.0.26 stable is a bug-fix release for the previously released 3.0.25 beta which introduced client-specific tags and included a couple of minor improvements. -------------------------------------------------------------------- ChangeLog for Privoxy -------------------------------------------------------------------- - Bug fixes: - Fixed crashes with "listen-addr :8118" (SF Bug #902). The regression was introduced in 3.0.25 beta and reported by Marvin Renich in Debian bug #834941. - General improvements: - Log when privoxy is toggled on or off via cgi interface. - Highlight the "Info: Now toggled " on/off log message in the Windows log viewer. - Highlight the loading actions/filter file log message in the Windows log viewer. - Mention client-specific tags on the toggle page as a potentionally more appropriate alternative. - Documentation improvements: - Update download section on the homepage. The downloads are available from the website now. - Add sponsor FAQ. - Remove obsolete reference to mailing lists hosted at SourceForge. - Update the "Before the Release" section of the developer manual. - Infrastructure improvements: - Add perl script to generate an RSS feed for the packages Submitted by "Unknown". - Build system improvements: - strptime.h: fix a compiler warning about ambiguous else. - configure.in: Check for Docbook goo on the BSDs as well. - GNUMakefile.in: Let the dok-user target remove temporary files. *** Version 3.0.25 beta *** - Bug fixes: - Always use the current toggle state for new requests. Previously new requests on reused connections inherited the toggle state from the previous request even though the toggle state could have changed. Reported by Robert Klemme. - Fixed two buffer-overflows in the (deprecated) static pcre code. These bugs are not considered security issues as the input is trusted. Found with afl-fuzz and ASAN. - General improvements: - Added support for client-specific tags which allow Privoxy admins to pre-define tags that are set for all requests from clients that previously opted in through the CGI interface. They are useful in multi-user setups where admins may want to allow users to disable certain actions and filters for themselves without affecting others. In single-user setups they are useful to allow more fine-grained toggling. For example to disable request blocking while still crunching cookies, or to disable experimental filters only. This is an experimental feature, the syntax and behaviour may change in future versions. Sponsored by Robert Klemme. - Dynamic filters and taggers now support a $listen-address variable which contains the address the request came in on. For external filters the variable is called $PRIVOXY_LISTEN_ADDRESS. Original patch contributed by pursievro. - Add client-header-tagger 'listen-address'. - Include the listen-address in the log message when logging new requests. Patch contributed by pursievro. - Turn invalid max-client-connections values into fatal errors. - The show-status page now shows whether or not dates before 1970 and after 2038 are expected to be handled properly. This is mainly useful for Privoxy-Regression-Test but could also come handy when dealing with time-related support requests. - On Mac OS X the thread id in log messages are more likely to be unique now. - When complaining about missing filters, the filter type is logged as well. - A couple of harmless coverity warnings were silenced (CID #161202, CID #161203, CID #161211). - Action file improvements: - Filtering is disabled for Range requests to let download resumption and Windows updates work with the default configuration. - Unblock ".ardmediathek.de/". Reported by ThTomate in #932. - Documentation improvements: - Add FAQ entry for crashes caused by memory limits. - Remove obsolete FAQ entry about a bug in PHP 4.2.3. - Mention the new mailing lists were appropriate. As the archives have not been migrated, continue to mention the archives at SF in the contacting section for now. - Note that the templates should be adjusted if Privoxy is running as intercepting proxy without getting all requests. - A bunch of links were converted to https://. - Rephrase onion service paragraph to make it more obvious that Tor is involved and that the whole website (and not just the homepage) is available as onion service. - Streamline the "More information" section on the homepage further by additionally ditching the link to the 'See also' section of the user manual. The section contains mostly links that are directly reachable from the homepage already and the rest is not significant enough to get a link from the homepage. - Change the add-header{} example to set the DNT header and use a complete section to make copy and pasting more convenient. Add a comment to make it obvious that adding the header is not recommended for obvious reasons. Using the DNT header as example was suggested by Leo Wzukw. - Streamline the support-and-service template Instead of linking to the various support trackers (whose URLs hopefully change soon), link to the contact section of the user manual to increase the chances that users actually read it. - Add a FAQ entry for tainted sockets. - More sections in the documentation have stable URLs now. - FAQ: Explain why 'ping config.privoxy.org' is not expected to reach a local Privoxy installation. - Note that donations done through Zwiebelfreunde e.V. currently can't be checked automatically. - Updated section regarding starting Privoxy under OS X. - Use dedicated start instructions for FreeBSD and ElectroBSD. - Removed release instructions for AIX. They haven't been working for years and unsurprisingly nobody seems to care. - Removed obsolete reference to the solaris-dist target. - Updated the release instructions for FreeBSD. - Removed unfinished release instructions for Amiga OS and HP-UX 11. - Added a pointer to the Cygwin Time Machine for getting the last release of Cygwin version 1.5 to use for building Privoxy on Windows. - Various typos have been fixed. - Infrastructure improvements: - The website is no longer hosted at SourceForge and can be reached through https now. - The mailing lists at SourceForge have been deprecated, you can subscribe to the new ones at: https://lists.privoxy.org/ - Migrating the remaining services from SourceForge is work in progress (TODO list item #53). - Build system improvements: - Add configure argument to optimistically redefine FD_SETSIZE with the intent to change the maximum number of client connections Privoxy can handle. Only works with some libcs. Sponsored by Robert Klemme. - Let the tarball-dist target skip files in ".git". - Let the tarball-dist target work in cwds other than current. - Make the 'clean' target faster when run from a git repository. - Include tools in the generic distribution. - Let the gen-dist target work in cwds other than current. - Sort find output that is used for distribution tarballs to get reproducible results. - Don't add '-src' to the name of the tar ball generated by the gen-dist target. The package isn't a source distribution but a binary package. While at it, use a variable for the name to reduce the chances that the various references get out of sync and fix the gen-upload target which was looking in the wrong directory. - Add regression-tests.action to the files that are distributed. - The gen-dist target which was broken since 2002 (r1.92) has been fixed. - Remove genclspec.sh which has been obsolete since 2009. - Remove obsolete reference to Redhat spec file. - Remove the obsolete announce target which has been commented out years ago. - Let rsync skip files if the checksums match. - Privoxy-Regression-Test: - Add a "Default level offset" directive which can be used to change the default level by a given value. This directive affects all tests located after it until the end of the file or a another "Default level offset" directive is reached. The purpose of this directive is to make it more convenient to skip similar tests in a given file without having to remove or disable the tests completely. - Let test level 17 depend on FEATURE_64_BIT_TIME_T instead of FEATURE_PTHREAD which has no direct connection to the time_t size. - Fix indentation in perldoc examples. - Don't overlook directives in the first line of the action file. - Bump version to 0.7. - Fix detection of the Privoxy version now that https:// is used for the website. ----------------------------------------------------------------- About Privoxy: ----------------------------------------------------------------- Privoxy is a non-caching web proxy with advanced filtering capabilities for enhancing privacy, modifying web page data and HTTP headers, controlling access, and removing ads and other obnoxious Internet junk. Privoxy has a flexible configuration and can be customized to suit individual needs and tastes. It has application for both stand-alone systems and multi-user networks. Privoxy is Free Software and licensed under the GNU GPLv2. Our TODO list is rather long. Helping hands and donations are welcome: * https://www.privoxy.org/faq/general.html#PARTICIPATE * https://www.privoxy.org/faq/general.html#DONATE At present, Privoxy is known to run on Windows 95 and later versions (98, ME, 2000, XP, Vista, Windows 7 etc.), GNU/Linux (RedHat, SuSE, Debian, Fedora, Gentoo, Slackware and others), Mac OS X (10.4 and upwards on PPC and Intel processors), OS/2, Haiku, DragonFly, ElectroBSD, FreeBSD, NetBSD, OpenBSD, Solaris, and various other flavors of Unix. In addition to the core features of ad blocking and cookie management, Privoxy provides many supplemental features, that give the end-user more control, more privacy and more freedom: * Supports "Connection: keep-alive". Outgoing connections can be kept alive independently from the client. Currently not available on all platforms. * Supports IPv6, provided the operating system does so too, and the configure script detects it. * Supports tagging which allows to change the behaviour based on client and server headers. * Can be run as an "intercepting" proxy, which obviates the need to configure browsers individually. * Sophisticated actions and filters for manipulating both server and client headers. * Can be chained with other proxies. * Integrated browser based configuration and control utility at http://config.privoxy.org/ (shortcut: http://p.p/). Browser-based tracing of rule and filter effects. Remote toggling. * Web page filtering (text replacements, removes banners based on size, invisible "web-bugs" and HTML annoyances, etc.) * Modularized configuration that allows for standard settings and user settings to reside in separate files, so that installing updated actions files won't overwrite individual user settings. * Support for Perl Compatible Regular Expressions in the configuration files, and a more sophisticated and flexible configuration syntax. * GIF de-animation. * Bypass many click-tracking scripts (avoids script redirection). * User-customizable HTML templates for most proxy-generated pages (e.g. "blocked" page). * Auto-detection and re-reading of config file changes. * Most features are controllable on a per-site or per-location basis. Home Page: https://www.privoxy.org/ - Privoxy Developers <pri...@li...> |
From: <pr...@ar...> - 2016-08-03 09:42:27
|
User @Faxopita since i cannot register to https://www.prxbx.com/forums/ due to ################################### Content Encoding Error The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression. The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression. Please contact the website owners to inform them of this problem. ################################## or maybe they don't like users from other countries than america, i have to ask you via this mailing-list. >From various post at https://www.prxbx.com/forums/ i see that you have developed some sort of https interface for privoxy and you're highly praised for this performance by some board users. >From your various post at https://www.prxbx.com/forums/ i can not find a single information - or maybe i overlooked it - what can be done with ProxHTTPSProxyMII. You wrote this https://sourceforge.net/p/ijbswa/mailman/message/35070785/ and i quote from your post: >You may want to filter HTTPS requests as well I know there have >been pains and cries recently about Privoxy not being able to filter >those requests. There is currently one working solution >thoughProxHTTPSProxyMII ><https://www.prxbx.com/forums/showthread.php?tid=2191&pid=18728#pid18728>that >I use on a daily basis with virtually no hiccup at all. It works >great and I confirm Privoxy is now able to block very nasty >encrypted requests. That says nothing to me. We (I !!) know more or less what can be done with Privoxy on the http side. Https traffic can only be blocked by domain names. Privoxy can't see the paths, nor the headers etc.. This kind of a simple domain blocking can also be done with uMask, dnsmasq or a hosts file. What can be done else or more with ProxHTTPSProxyMII? Regards. |
From: <pr...@ar...> - 2016-08-03 09:03:33
|
Dear developers, could you please provide me with a working example for this scenario: I have blocked www.bad.com for all sites on port 80 and port 443. Now I want to whitelist www.bad.com only for www.example.com:443. Since I only block or unblock by Top- and/or Second Level Domains, paths are irrelevant. Is this the only possible solution for https and maybe http traffic: {+block{test.} } www.bad.com {-block{test-2.} } www.example.com:443 As for http only there might be a solution by filtering the header. I have never done this before. Could you please provide me with a example? Thanks in advance. |
From: Fabian K. <fk...@fa...> - 2016-07-01 12:48:37
|
Haroon <ha...@sh...> wrote: > On Thu, 30 Jun 2016, Fabian Keil wrote: > > > Looks like this is working as expected (on the new list, not this one). > > The new mailing list is operating? Yes. Quoting the 3.0.25 beta announcement: | - The mailing lists at SourceForge have been deprecated, | you can subscribe to the new ones at: https://lists.privoxy.org/ Fabian |
From: Haroon <ha...@sh...> - 2016-07-01 02:45:07
|
On Thu, 30 Jun 2016, Fabian Keil wrote: > Looks like this is working as expected (on the new list, not this one). The new mailing list is operating? |
From: Fabian K. <fk...@fa...> - 2016-06-30 14:31:20
|
Fabian Keil <fk...@fa...> wrote: > Fabian Keil <fk...@fa...> wrote: > > > Ian Silvester <ian...@fa...> wrote: > > > > > And your fear proved correct - in replying to your list mail I received > > > the bounce from Hotmail again (reproduced below). It seems your fear is > > > correct; that a registered email address forwards to Hotmail and then > > > forwards to AOL. Annoying. I contacted the destination AOL address, and > > > not surprisingly I too received a bounce. > > > > > > Seems we're stuck with this :o( > > > > For now. > > > > When the new mailing lists are available (hopefully in May), users will > > have to explicitly subscribe to them again as the SourceForge terms of > > service don't cover migration to external services. Presumably the > > offending AOL user will not get the memo and stay behind. > > > > If this theory does not pan out or if the issue eventually reoccurs > > for another subscriber, controlling the Mailman instance will allow > > us to temporarily modify the subject_prefix to contain a subscriber-specific > > token that will make it into the bounce message. > > As it turns out, patching Mailman isn't necessary as it already supports > VERP which does this automatically (but is not enabled on this list): > https://wiki.list.org/DOC/So%20what%20is%20this%20VERP%20stuff Looks like this is working as expected (on the new list, not this one). Fabian |
From: Fabian K. <fk...@fa...> - 2016-06-27 14:34:01
|
Ian Silvester <ian...@fa...> wrote: > On Thu, 2 Jun 2016, at 16:30, Blaxton wrote: > > Yes, I think you should have commercial support as well. > > > > Most companies looking to have commercial support in case of bug or > > problem in proxy > > and need to have response time to reported problems. > > Understood, however this is a volunteer-run project whose team, in and > of itself, cannot scale to the needs of offering commercial-grade > support. The stage is open for any user or group thereof to set up such > an entity however! Many free software (and freeware) projects have a "commercial support" section on the website where qualifying third parties can get listed. Examples: https://www.freebsd.org/commercial/commercial.html https://www.debian.org/consultants/ We could have such a page as well. It would probably be quite a bit shorter than the lists above, but it could still be useful. > > Does it support ftp as well ? > > No it does not (so far as I know!). While Privoxy itself does not support ftp, clients that support it should be able to tunnel passive ftp through Privoxy by using CONNECT requests. Fabian |
From: Andrew J. C. <A.J...@ha...> - 2016-06-24 15:15:26
|
Ronald, Glad to see a fellow anti-spammer here and so far it's all good advice. > I'm not sure that I'm gfoing to be able to dedicate much time to > learning how to manage Privoxy for awhile yet... perhaps some > months... but now I have a very good starting point for when my time > permits me to get back to this. I've been using Privoxy since before it was Privoxy and it's shameful how little I understand of its more complex features, however you can filter the majority of unwanted web content with simple "domain" blocks and use the web interface to update the list. Here's how I do it. Privoxy 3.0.23 runs under OpenWRT 15.05.1 on my TP-LINK TL-WR1043ND and is 100% vanilla. I also host a PAC for proxy autoconfiguration on clients. Relevant non-default configuration options are logdir /home/log logfile privoxy.log toggle 1 enable-remote-toggle 1 enable-edit-actions 1 actionsfile user.action debug 1 debug 1024 debug 4096 debug 8192 The only file I change is user.action, for which I keep a readily accessible bookmark[1] (which may not be the same for all, so look for the [Edit] button under Actions Files: /etc/privoxy/user.action on the Status page[2]). In user.action I have unblock {-block} and block {+block} lists. Any time I have a new addition, I click [Add] and paste the new "domain". Most of my block additions come from watching the log which I store on non-volatile storage (USB drive). Like with mail logs, once you get used to the stream of information, you start to recognise the ad and tracker patterns. Looking at the URLs of ads which get to the browser provides the others. For example, the last tracker I noticed which wasn't Crunch:ed (but was Request:ed) showed as multiple lines like 2016-06-06 11:12:00.849 75bb8530 Request: s3.atas.io/5721c73bc6dd2c39378b456e Presuming that atas.io is a domain exclusively for ads and/or tracking - a safe presumption at least 95% of the time, I add the "domain" URL pattern .atas.io/ the the +block list. Note that this isn't a regexp, so it matches all requests for http://*.atas.io/*. In the same fashion, when Privoxy is filtering content from a site I want to see, I usually unblock the entire "domain", e.g. .bandcamp.com/ or .newegg.com/ That accounts for 90% of cases. The next 8+% are blocking ad/track subdomains on site which host their own, e.g. pixel.wp.com/ The remaining 1+% are the interesting ones, such as trying to clean up streaming media services or social networks (when alas they can't be blocked at the domain level), allowing animated GIFs, crunching cookies, etc. Of course all of this is on top of the the blocking and filtering done by Privoxy's defaults and supplemented by good browser hygiene. [1] http://config.privoxy.org/edit-actions-list?f=2 [2] http://config.privoxy.org/show-status -- -Andrew J. Caines- Unix Systems Architect A.J...@ha... "Machines take me by surprise with great frequency" - Alan Turing |
From: Haroon <ha...@sh...> - 2016-06-13 19:07:05
|
Well, this is what I ended up using: http://andrwe.org/scripting/bash/privoxy-blocklist So far so good. On Sat, 11 Jun 2016, Haroon wrote: > A couple months ago a post on the mailing list made me aware of the > existence of AdBlock to Privoxy conversion scripts and the like. I was > wondering if anyone had any suggestions regarding the best one out there, > as I've found a few different ones through web searches. > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic > patterns at an interface-level. Reveals which users, apps, and protocols are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > _______________________________________________ > Ijbswa-users mailing list > Ijb...@li... > https://lists.sourceforge.net/lists/listinfo/ijbswa-users > |
From: Haroon <ha...@sh...> - 2016-06-11 16:49:57
|
A couple months ago a post on the mailing list made me aware of the existence of AdBlock to Privoxy conversion scripts and the like. I was wondering if anyone had any suggestions regarding the best one out there, as I've found a few different ones through web searches. |
From: Ian S. <ian...@fa...> - 2016-06-02 20:43:34
|
On Thu, 2 Jun 2016, at 16:30, Blaxton wrote: > Yes, I think you should have commercial support as well. > > Most companies looking to have commercial support in case of bug or > problem in proxy > and need to have response time to reported problems. Understood, however this is a volunteer-run project whose team, in and of itself, cannot scale to the needs of offering commercial-grade support. The stage is open for any user or group thereof to set up such an entity however! > > I know Privoxy is none caching proxy, but can we disable all network > filtering > and have Privoxy act as relay and pass every thing through with no change > ? Yes, this is possible (though I'm not clear what it would achieve for you). Refer to documentation for details of altering the filtering Privoxy supplies. > Is It supporting HTTP and HTTPS connections ? HTTP only. Various solutions exist to chain Privoxy to other proxies to provide HTTPS decryption, but none so far exists that does not have downsides. > Does it support ftp as well ? No it does not (so far as I know!). Ian > > Thanks > > > ----- Original Message ----- > From: Fabian Keil <fk...@fa...> > To: ijb...@li... > Cc: Blaxton <bla...@ya...> > Sent: Thursday, June 2, 2016 4:36 AM > Subject: Re: [privoxy-users] Commercial Support > > Blaxton <bla...@ya...> wrote: > > > > Is there a company who provides commercial support for Privoxy ? > > A similar posting from Blaxton made it to the new privoxy-devel list: > https://lists.privoxy.org/pipermail/privoxy-devel/2016-May/000061.html > and I answered it there: > https://lists.privoxy.org/pipermail/privoxy-devel/2016-June/000062.html > > Fabian > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning reports. > https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > _______________________________________________ > Ijbswa-users mailing list > Ijb...@li... > https://lists.sourceforge.net/lists/listinfo/ijbswa-users |
From: Blaxton <bla...@ya...> - 2016-06-02 20:30:58
|
Yes, I think you should have commercial support as well. Most companies looking to have commercial support in case of bug or problem in proxy and need to have response time to reported problems. I know Privoxy is none caching proxy, but can we disable all network filtering and have Privoxy act as relay and pass every thing through with no change ? Is It supporting HTTP and HTTPS connections ? Does it support ftp as well ? Thanks ----- Original Message ----- From: Fabian Keil <fk...@fa...> To: ijb...@li... Cc: Blaxton <bla...@ya...> Sent: Thursday, June 2, 2016 4:36 AM Subject: Re: [privoxy-users] Commercial Support Blaxton <bla...@ya...> wrote: > Is there a company who provides commercial support for Privoxy ? A similar posting from Blaxton made it to the new privoxy-devel list: https://lists.privoxy.org/pipermail/privoxy-devel/2016-May/000061.html and I answered it there: https://lists.privoxy.org/pipermail/privoxy-devel/2016-June/000062.html Fabian |
From: Fabian K. <fk...@fa...> - 2016-06-02 09:36:23
|
Blaxton <bla...@ya...> wrote: > Is there a company who provides commercial support for Privoxy ? A similar posting from Blaxton made it to the new privoxy-devel list: https://lists.privoxy.org/pipermail/privoxy-devel/2016-May/000061.html and I answered it there: https://lists.privoxy.org/pipermail/privoxy-devel/2016-June/000062.html Fabian |
From: Blaxton <bla...@ya...> - 2016-06-01 11:25:32
|
Hi Is there a company who provides commercial support for Privoxy ? Thanks |
From: Fabian K. <fk...@fa...> - 2016-06-01 10:43:38
|
Rubén Llorente <po...@us...> wrote: > In gmane.comp.web.privoxy.user Fabian Keil <fk...@fa...> wrote: > > - The mailing lists at SourceForge have been deprecated, > > you can subscribe to the new ones at: https://lists.privoxy.org/ > > Do you plan to ask Gmane.org to carry the new lists? I don't and didn't do it for the old ones either. I would not be surprised if eventually somebody else would do it, though. Fabian |
From: Rubén L. <po...@us...> - 2016-05-31 13:56:13
|
In gmane.comp.web.privoxy.user Fabian Keil <fk...@fa...> wrote: > - The mailing lists at SourceForge have been deprecated, > you can subscribe to the new ones at: https://lists.privoxy.org/ Do you plan to ask Gmane.org to carry the new lists? -- OpenPGP Key Fingerprint: BB5A C2A2 2CAD ACB7 D50D C081 1DB9 6FC4 5AB7 92FA |
From: Fabian K. <fk...@fa...> - 2016-05-31 12:27:59
|
Announcing Privoxy 3.0.25 beta -------------------------------------------------------------------- Privoxy 3.0.25 beta introduces client-specific tags and includes a couple of minor improvements. It will be followed by a stable release in the near future. -------------------------------------------------------------------- ChangeLog for Privoxy -------------------------------------------------------------------- - Bug fixes: - Always use the current toggle state for new requests. Previously new requests on reused connections inherited the toggle state from the previous request even though the toggle state could have changed. Reported by Robert Klemme. - Fixed two buffer-overflows in the (deprecated) static pcre code. These bugs are not considered security issues as the input is trusted. Found with afl-fuzz and ASAN. - General improvements: - Added support for client-specific tags which allow Privoxy admins to pre-define tags that are set for all requests from clients that previously opted in through the CGI interface. They are useful in multi-user setups where admins may want to allow users to disable certain actions and filters for themselves without affecting others. In single-user setups they are useful to allow more fine-grained toggling. For example to disable request blocking while still crunching cookies, or to disable experimental filters only. This is an experimental feature, the syntax and behaviour may change in future versions. Sponsored by Robert Klemme. - Dynamic filters and taggers now support a $listen-address variable which contains the address the request came in on. For external filters the variable is called $PRIVOXY_LISTEN_ADDRESS. Original patch contributed by pursievro. - Add client-header-tagger 'listen-address'. - Include the listen-address in the log message when logging new requests. Patch contributed by pursievro. - Turn invalid max-client-connections values into fatal errors. - The show-status page now shows whether or not dates before 1970 and after 2038 are expected to be handled properly. This is mainly useful for Privoxy-Regression-Test but could also come handy when dealing with time-related support requests. - On Mac OS X the thread id in log messages are more likely to be unique now. - When complaining about missing filters, the filter type is logged as well. - A couple of harmless coverity warnings were silenced (CID #161202, CID #161203, CID #161211). - Action file improvements: - Filtering is disabled for Range requests to let download resumption and Windows updates work with the default configuration. - Unblock ".ardmediathek.de/". Reported by ThTomate in #932. - Documentation improvements: - Add FAQ entry for crashes caused by memory limits. - Remove obsolete FAQ entry about a bug in PHP 4.2.3. - Mention the new mailing lists were appropriate. As the archives have not been migrated, continue to mention the archives at SF in the contacting section for now. - Note that the templates should be adjusted if Privoxy is running as intercepting proxy without getting all requests. - A bunch of links were converted to https://. - Rephrase onion service paragraph to make it more obvious that Tor is involved and that the whole website (and not just the homepage) is available as onion service. - Streamline the "More information" section on the homepage further by additionally ditching the link to the 'See also' section of the user manual. The section contains mostly links that are directly reachable from the homepage already and the rest is not significant enough to get a link from the homepage. - Change the add-header{} example to set the DNT header and use a complete section to make copy and pasting more convenient. Add a comment to make it obvious that adding the header is not recommended for obvious reasons. Using the DNT header as example was suggested by Leo Wzukw. - Streamline the support-and-service template Instead of linking to the various support trackers (whose URLs hopefully change soon), link to the contact section of the user manual to increase the chances that users actually read it. - Add a FAQ entry for tainted sockets. - More sections in the documentation have stable URLs now. - FAQ: Explain why 'ping config.privoxy.org' is not expected to reach a local Privoxy installation. - Note that donations done through Zwiebelfreunde e.V. currently can't be checked automatically. - Updated section regarding starting Privoxy under OS X. - Use dedicated start instructions for FreeBSD and ElectroBSD. - Removed release instructions for AIX. They haven't been working for years and unsurprisingly nobody seems to care. - Removed obsolete reference to the solaris-dist target. - Updated the release instructions for FreeBSD. - Removed unfinished release instructions for Amiga OS and HP-UX 11. - Added a pointer to the Cygwin Time Machine for getting the last release of Cygwin version 1.5 to use for building Privoxy on Windows. - Various typos have been fixed. - Infrastructure improvements: - The website is no longer hosted at SourceForge and can be reached through https now. - The mailing lists at SourceForge have been deprecated, you can subscribe to the new ones at: https://lists.privoxy.org/ - Migrating the remaining services from SourceForge is work in progress (TODO list item #53). - Build system improvements: - Add configure argument to optimistically redefine FD_SETSIZE with the intent to change the maximum number of client connections Privoxy can handle. Only works with some libcs. Sponsored by Robert Klemme. - Let the tarball-dist target skip files in ".git". - Let the tarball-dist target work in cwds other than current. - Make the 'clean' target faster when run from a git repository. - Include tools in the generic distribution. - Let the gen-dist target work in cwds other than current. - Sort find output that is used for distribution tarballs to get reproducible results. - Don't add '-src' to the name of the tar ball generated by the gen-dist target. The package isn't a source distribution but a binary package. While at it, use a variable for the name to reduce the chances that the various references get out of sync and fix the gen-upload target which was looking in the wrong directory. - Add regression-tests.action to the files that are distributed. - The gen-dist target which was broken since 2002 (r1.92) has been fixed. - Remove genclspec.sh which has been obsolete since 2009. - Remove obsolete reference to Redhat spec file. - Remove the obsolete announce target which has been commented out years ago. - Let rsync skip files if the checksums match. - Privoxy-Regression-Test: - Add a "Default level offset" directive which can be used to change the default level by a given value. This directive affects all tests located after it until the end of the file or a another "Default level offset" directive is reached. The purpose of this directive is to make it more convenient to skip similar tests in a given file without having to remove or disable the tests completely. - Let test level 17 depend on FEATURE_64_BIT_TIME_T instead of FEATURE_PTHREAD which has no direct connection to the time_t size. - Fix indentation in perldoc examples. - Don't overlook directives in the first line of the action file. - Bump version to 0.7. - Fix detection of the Privoxy version now that https:// is used for the website. ----------------------------------------------------------------- About Privoxy: ----------------------------------------------------------------- Privoxy is a non-caching web proxy with advanced filtering capabilities for enhancing privacy, modifying web page data and HTTP headers, controlling access, and removing ads and other obnoxious Internet junk. Privoxy has a flexible configuration and can be customized to suit individual needs and tastes. It has application for both stand-alone systems and multi-user networks. Privoxy is Free Software and licensed under the GNU GPLv2. Our TODO list is rather long. Helping hands and donations are welcome: * https://www.privoxy.org/faq/general.html#PARTICIPATE * https://www.privoxy.org/faq/general.html#DONATE At present, Privoxy is known to run on Windows 95 and later versions (98, ME, 2000, XP, Vista, Windows 7 etc.), GNU/Linux (RedHat, SuSE, Debian, Fedora, Gentoo, Slackware and others), Mac OS X (10.4 and upwards on PPC and Intel processors), OS/2, Haiku, DragonFly, ElectroBSD, FreeBSD, NetBSD, OpenBSD, Solaris, and various other flavors of Unix. In addition to the core features of ad blocking and cookie management, Privoxy provides many supplemental features, that give the end-user more control, more privacy and more freedom: * Supports "Connection: keep-alive". Outgoing connections can be kept alive independently from the client. Currently not available on all platforms. * Supports IPv6, provided the operating system does so too, and the configure script detects it. * Supports tagging which allows to change the behaviour based on client and server headers. * Can be run as an "intercepting" proxy, which obviates the need to configure browsers individually. * Sophisticated actions and filters for manipulating both server and client headers. * Can be chained with other proxies. * Integrated browser based configuration and control utility at http://config.privoxy.org/ (shortcut: http://p.p/). Browser-based tracing of rule and filter effects. Remote toggling. * Web page filtering (text replacements, removes banners based on size, invisible "web-bugs" and HTML annoyances, etc.) * Modularized configuration that allows for standard settings and user settings to reside in separate files, so that installing updated actions files won't overwrite individual user settings. * Support for Perl Compatible Regular Expressions in the configuration files, and a more sophisticated and flexible configuration syntax. * GIF de-animation. * Bypass many click-tracking scripts (avoids script redirection). * User-customizable HTML templates for most proxy-generated pages (e.g. "blocked" page). * Auto-detection and re-reading of config file changes. * Most features are controllable on a per-site or per-location basis. Home Page: https://www.privoxy.org/ - Privoxy Developers <pri...@li...> |
From: Ronald F. G. <rf...@tr...> - 2016-05-07 21:11:50
|
In message <dbc...@ic...>, Vanderdenduur <rv...@ic...> wrote: >It's sad to say, but I believe one must commit time to understand how >Privoxy works, how to use it and how to enhance its power. It is not sad. That's just reality. Anything powerful, flexible, and useful takes time to understand properly. The famous phrase is "There is no royal road to geometry." I understand this well. Anyway, thank you for all of the useful information you have provided. I'm not sure that I'm gfoing to be able to dedicate much time to learning how to manage Privoxy for awhile yet... perhaps some months... but now I have a very good starting point for when my time permits me to get back to this. Regards, rfg |