From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. fab1f85783abd330657d6c0d331848e50347ca4c
Date: Tue, 15 Apr 2014 21:16:57 +0200 [thread overview]
Message-ID: <20140415191657.7D80E20AD0@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1492 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, master has been updated
via fab1f85783abd330657d6c0d331848e50347ca4c (commit)
from eae92b2bafe3a94a3c6c616f8ff02c6fa013e97a (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 fab1f85783abd330657d6c0d331848e50347ca4c
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue Apr 15 21:16:14 2014 +0200
strongswan: Update to 5.1.3.
Fixes CVE-2014-2338.
-----------------------------------------------------------------------
Summary of changes:
lfs/strongswan | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/lfs/strongswan b/lfs/strongswan
index 600a16f..f9f6e78 100644
--- a/lfs/strongswan
+++ b/lfs/strongswan
@@ -24,7 +24,7 @@
include Config
-VER = 5.1.2
+VER = 5.1.3
THISAPP = strongswan-$(VER)
DL_FILE = $(THISAPP).tar.bz2
@@ -48,7 +48,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = d45a2e89c624bceaf2e53c9b9cdddf83
+$(DL_FILE)_MD5 = 1d1c108775242743cd8699215b2918c3
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-04-15 19:16 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=20140415191657.7D80E20AD0@argus.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