From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 2.x development tree branch, core60, created. 1346863ac7cbf67b38d6209a6b0ab3bab565386c
Date: Fri, 01 Jun 2012 12:59:39 +0200 [thread overview]
Message-ID: <20120601105939.381DE20181@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1062 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, core60 has been created
at 1346863ac7cbf67b38d6209a6b0ab3bab565386c (commit)
- Log -----------------------------------------------------------------
commit 1346863ac7cbf67b38d6209a6b0ab3bab565386c
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Jun 1 12:54:24 2012 +0200
core60: add strongswan security update.
commit 6105282debd636dd5634f6e487afbeb02b51a69b
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Jun 1 12:47:07 2012 +0200
strongswan: security update to 4.6.4 (fix CVE-2012-2388).
RSA signature verification vulnerability
see http://http://www.strongswan.org/blog/2012/05/31/strongswan-4.6.4-released-%28cve-2012-2388%29.html for details.
-----------------------------------------------------------------------
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2012-06-01 10:59 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=20120601105939.381DE20181@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