From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] privoxy: Update to 3.0.24
Date: Tue, 29 Mar 2016 18:54:26 +0100 [thread overview]
Message-ID: <1459274066.30749.216.camel@ipfire.org> (raw)
In-Reply-To: <56FAA3BC.6010102@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
Hi,
I am still not sure what benefit this will bring to the IPFire users. What will
it bring to addition of squidGuard and the "URL Filter"?
I know that it can remove ads within the HTML, but as pretty much most of the
websites are encrypted where I think this would be useful, what is the point?
Technically I have nothing against it. I just cannot see where the benefit is to
build and maintain this.
-Michael
On Tue, 2016-03-29 at 17:48 +0200, Matthias Fischer wrote:
> Hi,
>
> On 29.03.2016 16:04, Michael Tremer wrote:
> >
> > Hi,
> >
> > indeed. Never bundle a library. Never. Never. Never.
> >
> > PCRE had some severe security issues recently and I assume that these are
> > not
> > fixed in the privoxy release tarball. If we fix the issues in pcre it will
> > automatically be fixed in privoxy too when dynamically linked.
> Thanks - I thought of something like that but wasn't sure.
>
> Prior to my question I deleted "--disable-dynamic-pcre" from the privoxy
> lfs-file and will keep it this way.
>
> By the way - feedback is sparse, as ever - but how are the chances of
> 'privoxy' becoming an official addon? Anything I could improve?
>
> Best,
> Matthias
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-03-29 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 0:11 Matthias Fischer
2016-01-24 19:42 ` Michael Tremer
2016-01-24 20:21 ` Matthias Fischer
2016-01-25 20:25 ` Matthias Fischer
2016-03-29 14:04 ` Michael Tremer
2016-03-29 15:48 ` Matthias Fischer
2016-03-29 17:54 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1459274066.30749.216.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox