From 126d4870b217c13936ec344ed4393c55082ac3b9 Mon Sep 17 00:00:00 2001 From: Francis Lachapelle Date: Wed, 11 Dec 2013 13:48:20 -0500 Subject: [PATCH] Prepare release 4.1.0 --- NEWS.asciidoc | 4 ++-- debian/changelog | 6 ++++++ ...PacketFence_Network_Devices_Configuration_Guide.asciidoc | 4 ++-- docs/docinfo.xml | 2 +- 4 files changed, 11 insertions(+), 5 deletions(-) diff --git a/NEWS.asciidoc b/NEWS.asciidoc index be91d0e08974..b9e94f3cf2de 100644 --- a/NEWS.asciidoc +++ b/NEWS.asciidoc @@ -11,7 +11,7 @@ This is a list of noteworthy changes across releases. For more details and developer visible changes see the ChangeLog file. For a list of compatibility related changes see the UPGRADE.asciidoc file. -Version 4.1.0 released on 2013-MM-DD +Version 4.1.0 released on 2013-12-11 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ New Features @@ -20,7 +20,7 @@ New Features * Portal profiles can be filtered by switches * Proxy interception * New pfcmd command fixpermissions -* Added a Null Authenication Source +* Added a "Null" authenication source * Displayed columns of nodes are now customizable * Create a single node or import multiple nodes from a CSV file from the Web admin * LDAP authentication sources can now filter by group membership using a second LDAP query diff --git a/debian/changelog b/debian/changelog index e36c7a519844..e45bd5236159 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +packetfence (4.1.0) unstable; urgency=low + + * Version 4.1.0 + + -- Francis Lachapelle Wed, 11 Dec 2013 12:00:00 -0400 + packetfence (4.0.6) unstable; urgency=low * Version 4.0.6 diff --git a/docs/PacketFence_Network_Devices_Configuration_Guide.asciidoc b/docs/PacketFence_Network_Devices_Configuration_Guide.asciidoc index 37d768cac4e9..e998dd6a9ee8 100644 --- a/docs/PacketFence_Network_Devices_Configuration_Guide.asciidoc +++ b/docs/PacketFence_Network_Devices_Configuration_Guide.asciidoc @@ -47,7 +47,7 @@ Note on Inline enforcement support ---------------------------------- There is no need to follow the instructions in this guide if you plan on deploying in inline -enforcement, except radius inline. In this case all you need to do is to have a flat layer 2 network up to +enforcement, except RADIUS inline. In this case all you need to do is to have a flat layer 2 network up to PacketFence's inline interface with no other gateway available for devices to reach out to the Internet. @@ -1130,7 +1130,7 @@ Dell Force 10 ^^^^^^^^ -PacketFence supports this switch using radiusi mac-auth and 802.1x +PacketFence supports this switch using RADIUS, MAC-Authentication and 802.1x. Global config settings diff --git a/docs/docinfo.xml b/docs/docinfo.xml index c4824483c4bd..7ef185ee3153 100644 --- a/docs/docinfo.xml +++ b/docs/docinfo.xml @@ -1,7 +1,7 @@ Version 4.1.0 - December 2013 for version 4.1.0 -2013-12-05 +2013-12-11 Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".