From: The IPFire Project <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: IPFire 2.13 - Core Update 74 [The Christmas Release]
Date: Sun, 22 Dec 2013 23:14:17 +0100 [thread overview]
Message-ID: <mailman.82.1387750549.26666.ipfire-announce@lists.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2077 bytes --]
Christmas is approaching and as an early gift we would like to give to
all those who are celebrating our brand new release IPFire 2.13 Core
Update 74. It comes with a bunch of minor updates and fixes some minor
bugs.
Update to squid 3.3.11
The latest maintenance update [1] of the Web Proxy package squid has
been applied. The max. number of filedescriptors has again been
increased to 1048576 [2] and the issue that it was impossible for the
squid daemon to set the desired configuration value has been fixed
([3]).
VPN service updates
The OpenVPN package has been updated to version 2.3.2 [4, 5].
strongswan, the package responsible for IPsec VPN connections, has been
updated to version 5.1.1 [6].
Increasing RSA key sizes
The HTTPS key and certificate that are used for communitcating with our
IPFire Web User Interface has been increased to 4096 bits. This follows
the general advice by various authorities. New installations will
automatically generate a bigger key.
We recommend that everyone updates to this version of IPFire as soon as
possible and would like to encourage everyone who downloads and uses
IPFire to get involved [8,9] in any way they can. Please consider
donating [10] or joining the project community!
Merry Christmas,
-The IPFire Team
[1] http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=a408e02da29d32d72a570112caec8544f0474f51
[2] http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=4f160f04cb819cafd9b4ddc53ccb24d48668aa92
[3] https://bugzilla.ipfire.org/show_bug.cgi?id=10445
[4] http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=1e6ce289bd8520b07897fa0f70253c8e56acc188
[5] https://community.openvpn.net/openvpn/wiki/ChangesInOpenvpn23
[6] http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=ec985733a532fb257e75fd75a10746fe9c8cfb80
[7] http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=325aa1e1f4b1948fe3dbd1bb6c65d056b1bebe29
[8] http://www.ipfire.org/getinvolved
[9] http://planet.ipfire.org/post/job-exchange-what-is-it
[10] http://www.ipfire.org/donation
reply other threads:[~2013-12-22 22:14 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=mailman.82.1387750549.26666.ipfire-announce@lists.ipfire.org \
--to=ipfire-announce@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