public inbox for ipfire-announce@lists.ipfire.org
 help / color / mirror / Atom feed
From: "The IPFire Project." <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: [IPFire Announcement] Core Update 58 released
Date: Thu, 17 May 2012 13:55:44 +0200	[thread overview]
Message-ID: <mailman.95.1337330185.1002.ipfire-announce@lists.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1819 bytes --]

In case you missed the announcement on the front page:

It is time for the next maintainance update of the IPFire series 2 which
is called Core Update 58. This update comes with cryptodev, a bunch of
security fixes and minor bugfixes.

cryptodev has been ported from BSD and provides the kernel crypto system
to the userspace. The advantages we gain from that is much faster
hashing, encryption and decryption of data. On a normal system, the
performance will double, on systems that come with crypto processors
like VIA Padlock or Marvell CESA, the speed will be significantly higher
and the CPU load will be much lower. More information about cryptodev
can be found on our wiki.

The update is shipping fixes for security issues in two packages:
openssl (0.9.8u) and libpng (1.2.46).

More things:
    strongswan: 4.6.2 – Minor bugfixes (#10037).
    fireinfo: 2.1.4 – Improved detection of number of CPUs on ARM devices.
    openvpn: Update to 2.2.2 and now compiled with —enable-password-save (#10036).
    vim: A small line at the bottom shows more information (#10021).
    The hardware database, GeoIP database and usb_modeswitch database have been updated to enable newest hardware to work with IPFire.


Updated addons since the last Core Update:
    samba (addressed two security problems) details are to be found here.
    clamav 0.97.4
    git 1.7.9.3
    pound, which is now able to handle more than one certificate per IP choosing them by their common names or SANs.

We recommend to update to this version as soon as possible, because we
think it is the best version of IPFire that has ever been released. If
you think so as well, please consider a small donation.

Please notice the recent posts on the planet, where the developers talk
about geeky stuff.



                 reply	other threads:[~2012-05-17 11:55 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.95.1337330185.1002.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