From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core74, created. 5cd3a05bf0653726834489c87b80064584e6073b
Date: Mon, 16 Dec 2013 10:18:57 +0100 [thread overview]
Message-ID: <20131216091859.5FE042080B@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1952 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, core74 has been created
at 5cd3a05bf0653726834489c87b80064584e6073b (commit)
- Log -----------------------------------------------------------------
commit 5cd3a05bf0653726834489c87b80064584e6073b
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sat Dec 14 22:01:16 2013 +0100
finalize core 74.
commit 6c859e038223d4c6ec8535b7b7e635d9ef7fac1f
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Dec 12 21:20:56 2013 +0100
core74: Add httpscert script.
commit 325aa1e1f4b1948fe3dbd1bb6c65d056b1bebe29
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Dec 12 21:18:56 2013 +0100
httpscert: Increase size of the RSA key to 4096.
RSA keys with length of 1024 bits are considered weak.
commit a1365ee37ccffa2be499d483ff1356d9f71013de
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Dec 12 21:17:53 2013 +0100
httpscert: Use regular random source.
Previous to this patch, the kernel image file and internal
configuration settings have been used as a source for random
data, which is not random at all.
commit cfb00625b8224e929ecc4a2610bbe153f7ead475
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Dec 12 21:15:24 2013 +0100
strongswan: Disable rdrand plugin.
Disabled because of security concerns.
commit dfb1bfaf7b88a914ae2a384a0f30bdafaebc9125
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Dec 11 21:59:22 2013 +0100
Always create squid.conf.
In some cases, /var/ipfire/proxy/squid.conf does not belong to
nobody:nobody, so we do this explicitely.
-----------------------------------------------------------------------
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-12-16 9:18 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=20131216091859.5FE042080B@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