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 2.13 - Core Update 75 released
Date: Sun, 12 Jan 2014 20:34:41 +0100	[thread overview]
Message-ID: <mailman.138.1389555326.26666.ipfire-announce@lists.ipfire.org> (raw)

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

http://www.ipfire.org/news/ipfire-2-13-core-update-75-released

So it is a new year and here is the first update of 2014: IPFire 2.13
Core Update 75. It comes with urgent bug fixes that solve problems
introduced in the previous update.


OpenVPN TLS certificate validation

Due to a change in OpenVPN 2.3, the common name of the certificate of
the user that was connection was formatted in an other way than before.
This led to that the certificate could not be properly validated because
it was searched for one with a different name.

This update ships a fixed version of the verify script that can work
with both formats of the common name.


OpenVPN connection configuration

Because of a related cause, the route configuration was not pushed to
some clients when they connected. This issue that is filed under bug id
#10323 [1] and has been addressed in this update.


Pakfire locking up

When pakfire receives an empty mirror list, the process stalls while it
is checking for a working mirror server. A fix for this problem has been
introduced that will download packages from the main server, when none
of the mirror servers is available.


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 [2] in any way they can. Please consider donating
[3] or joining the project community!

[1] https://bugzilla.ipfire.org/show_bug.cgi?id=10323
[2] http://www.ipfire.org/getinvolved
[3] http://www.ipfire.org/donation


                 reply	other threads:[~2014-01-12 19:34 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.138.1389555326.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