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 73
Date: Tue, 26 Nov 2013 21:16:55 +0100	[thread overview]
Message-ID: <mailman.51.1385497999.26666.ipfire-announce@lists.ipfire.org> (raw)

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

IPFire 2.13 - Core Update 73 comes with a bunch of smaller bugfixes and
updates. The most important ones of these are updates of the squid web
proxy server, openssh and the PHP Hypertext Processor. It is recommend
to update as soon as possible.


squid 3.3

The squid web proxy server has been updated to version 3.3.10 [1]. The
most notable changes since the current version of squid running in
IPFire are better SMP scalability, an updated logging infrastructure and
fixes all over the place.

The transparent mode has been dropped in favour of the more general
intercept mode, which requires a different port than for the transparent
mode. There is no intervention by the user required, when updating your
IPFire system, as the a new port for this service will automatically
chosen and configured.

Also, the default number of file descriptors has been increased for new
installations.


php 5.3.27

PHP has been updated to version 5.3.27, which fixes a whole bunch of
bugs as usual. Modules for ZIP and sqlite2 are compiled in now.


Misc. changes

* openssh has been updated to version 6.4p1.
* Wireless Client: You can now use an apostrophe (') in the SSID string
  (#10427). There has also been some help added for the priority option
  (#10428).
* Static Routes: Fix validating IP addresses (e.g. 10.0.0.0 was
  recognized as a wrong IP address).
* Formerly [2], when a network interface for the blue or orange network
  zone has been assigned, but blue or orange were not enabled, various
  CGI scripts crashed. This has been fixed now.


The release of this Core Update was delayed because the developers are
currently working on the next major version of IPFire. To support us
all, please consider sending us a donation [3] or join the team to help
busting bugs!


[1] http://www.squid-cache.org/Versions/v3/3.3/RELEASENOTES.html
[2] http://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=d3527a38c16451d956c623901d11472ebbe47e98
[3] http://www.ipfire.org/donate


                 reply	other threads:[~2013-11-26 20:16 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.51.1385497999.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