From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] privoxy: Update to 3.0.24
Date: Sun, 24 Jan 2016 19:42:55 +0000 [thread overview]
Message-ID: <1453664575.585.132.camel@ipfire.org> (raw)
In-Reply-To: <1453594308-7026-1-git-send-email-matthias.fischer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2479 bytes --]
Hi,
there is no privoxy in IPFire :)
What branch is this patch for?
-Michael
On Sun, 2016-01-24 at 01:11 +0100, Matthias Fischer wrote:
> Changelog - in short:
> - Security fixes (denial of service):
> - Prevent invalid reads in case of corrupt chunk-encoded content.
> CVE-2016-1982. Bug discovered with afl-fuzz and AddressSanitizer.
> - Remove empty Host headers in client requests.
> Previously they would result in invalid reads. CVE-2016-1983.
> Bug discovered with afl-fuzz and AddressSanitizer.
>
> Also several bug fixes as well as general, action file, and
> documentation improvements.
>
> For details see:
> http://www.privoxy.org/announce.txt
>
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
> lfs/privoxy | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/lfs/privoxy b/lfs/privoxy
> index bc4848a..de650a2 100644
> --- a/lfs/privoxy
> +++ b/lfs/privoxy
> @@ -1,7 +1,7 @@
> ####################################################################
> ###########
> #
> #
> # IPFire.org - A linux based firewall
> #
> -# Copyright (C) 2007-2015 IPFire Team <info(a)ipfire.org>
> #
> +# Copyright (C) 2007-2016 IPFire Team <info(a)ipfire.org>
> #
> #
> #
> # This program is free software: you can redistribute it and/or
> modify #
> # it under the terms of the GNU General Public License as published
> by #
> @@ -24,14 +24,14 @@
>
> include Config
>
> -VER = 3.0.23
> +VER = 3.0.24
> THISAPP = privoxy-$(VER)
> DL_FILE = $(THISAPP)-stable-src.tar.gz
> DL_FROM = $(URL_IPFIRE)
> DIR_APP = $(DIR_SRC)/$(THISAPP)
> TARGET = $(DIR_INFO)/$(THISAPP)
> PROG = privoxy
> -PAK_VER = 2
> +PAK_VER = 3
>
> DEPS = ""
>
> @@ -43,7 +43,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_MD5 = bbe47d5ff1a54d9f9fc93a160532697f
> +$(DL_FILE)_MD5 = 44a47d1a5000db8cccd61ace0e25e7f7
>
> install : $(TARGET)
>
> @@ -53,7 +53,7 @@ download :$(patsubst %,$(DIR_DL)/%,$(objects))
>
> md5 : $(subst %,%_MD5,$(objects))
>
> -dist:
> +dist:
> $(PAK)
>
> ####################################################################
> ###########
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-24 19:42 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 [this message]
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
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=1453664575.585.132.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