From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 3494b0cebb5ae1fd030d42017cd34c0b5870a13f
Date: Tue, 24 Jan 2017 14:00:43 +0000 [thread overview]
Message-ID: <20170124140043.B42B51078E80@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1797 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 3494b0cebb5ae1fd030d42017cd34c0b5870a13f (commit)
from ba957627e2d8b69191984f12c995bba926b0331d (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 3494b0cebb5ae1fd030d42017cd34c0b5870a13f
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue Jan 24 13:56:45 2017 +0000
tor: Update to 0.2.9.9
Includes a fix for a denial-of-service vulnerability among
many more various fixes.
Fixes #11281
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/tor | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/lfs/tor b/lfs/tor
index 5f39d78..be812e0 100644
--- a/lfs/tor
+++ b/lfs/tor
@@ -24,7 +24,7 @@
include Config
-VER = 0.2.8.10
+VER = 0.2.9.9
THISAPP = tor-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = tor
-PAK_VER = 18
+PAK_VER = 19
DEPS = ""
@@ -44,7 +44,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = f5762c9eeb7bc68a6405cd5d6a53b5d7
+$(DL_FILE)_MD5 = d9d8a2d1f65c151eb2b448f6a93fc326
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2017-01-24 14:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170124140043.B42B51078E80@git01.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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