Please find, for review, the debconf templates of radiusd-livingston. This review will last from Thursday, May 10, 2007 to Sunday, May 20, 2007. Please send reviews as unified diffs (diff -u) against the original files. Comments about your proposed changes will be appreciated. Your review should be sent as an answer to this mail. When appropriate, I will send intermediate requests for review, with "[RFRn]" (n>=2) as a subject tag. When we will reach a consensus, I send a "Last Chance For Comments" mail with "[LCFC]" as a subject tag. Finally, the reviewed templates will be sent to the package maintainer as a bug report, and a mail will be sent to this list with "[BTS]" as a subject tag. Some addtional comments ... I took a few liberties in rewriting the control file. Specifically I added a paragraph to give a bit more explanation about RADIUS servers in general. This may not be appropriate but I like the long description to provide solid info. Users perusing 'apt-cache show' or equivalent will then have a better idea about what the package does. I rewrote the templates file, but my guess is that this file will become unnecessary. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422325. There are three config files (users, clients, and proxy) that I believe should be written to /etc/radiusd-livingston as part of the install process. Instead they are written to /u/s/doc/radiusd-livingston/examples and the user is asked, via debconf notes, to copy them manually to /etc/radiusd-livingston. I would suggest that the three config files - users, clients, proxy - be left intact with examples but commented out completely and copied to /etc/radiusd-livingston as part of the install. A new file README.Debian could be added instructing the user to edit these files in /etc/radiusd-livingston. It is interesting because debian/rules has some commented out lines that do copy these three config files to /etc/radiusd-livingston. Kevin -- Kevin Coyner GnuPG key: 1024D/8CE11941
Template: radiusd-livingston/configure_clients Type: note _Description: You must configure clients for your RADIUS server. Copy the example file /usr/share/doc/radiusd-livingston/examples/clients to /etc/radiusd-livingston/clients and edit it for each RADIUS client you intend to service. Template: radiusd-livingston/configure_users Type: note _Description: You must configure users for your RADIUS server. Copy the example file /usr/share/doc/radiusd-livingston/examples/users to /etc/radiusd-livingston/users and edit it for each RADIUS user you intend to service.
--- ../radiusd-livingston.old/debian/templates 2007-05-06 06:34:10.000000000 -0400 +++ debian/templates 2007-05-09 21:19:21.000000000 -0400 @@ -1,14 +1,13 @@ Template: radiusd-livingston/configure_clients Type: note -_Description: You must configure your RADIUS server. - Use /usr/share/doc/radiusd-livingston/examples/clients - to generate a /etc/radiusd-livingston/clients for each - RADIUS client you service. +_Description: You must configure clients for your RADIUS server. + Copy the example file /usr/share/doc/radiusd-livingston/examples/clients to + /etc/radiusd-livingston/clients and edit it for each RADIUS client you intend + to service. Template: radiusd-livingston/configure_users Type: note -_Description: You must configure your RADIUS server. - Use /usr/share/doc/radiusd-livingston/examples/users - to generate a /etc/radiusd-livingston/users for each - RADIUS user you service. - +_Description: You must configure users for your RADIUS server. + Copy the example file /usr/share/doc/radiusd-livingston/examples/users to + /etc/radiusd-livingston/users and edit it for each RADIUS user you intend to + service. --- ../radiusd-livingston.old/debian/control 2007-05-06 06:34:10.000000000 -0400 +++ debian/control 2007-05-09 20:59:12.000000000 -0400 @@ -12,8 +12,19 @@ Replaces: radius-server Provides: radius-server Description: Remote Authentication Dial-In User Service (RADIUS) server - Provides the RADIUS server from Lucent Technologies Inc, formerly - Livingston Enterprises Inc. + RADIUS is an AAA (authentication, authorization and accounting) protocol for + managing client access to network services. This version of the RADIUS server + is from Lucent Technologies Inc., formerly known as Livingston Enterprises + Inc., and is described by RFC's 2865 to 2869. . - RADIUS is a means of managing clients' access to network services, and - is described by RFCs 2865 to 2869. + Some ISP's (commonly modem, DSL, or wireless 802.11 services) require you to + enter a username and password in order to connect to the Internet. Before + access to the network is granted, this information is passed to a Network + Access Server (NAS) device over the link-layer protocol and then to a RADIUS + server over the RADIUS protocol. The RADIUS server checks that the + information is correct using authentication schemes like PAP, CHAP or EAP. If + accepted, the server will then authorize access to the ISP system and select + an IP address, L2TP parameters, etc. + . + RADIUS is also commonly used for accounting purposes so that the users can be + billed accordingly.
Source: radiusd-livingston
Section: net
Priority: optional
Maintainer: Paul Martin <pm@debian.org>
Build-Depends: debhelper (>>5), libdb4.5-dev
Standards-Version: 3.7.2
Package: radiusd-livingston
Architecture: any
Depends: ${shlibs:Depends}
Conflicts: radius-server
Replaces: radius-server
Provides: radius-server
Description: Remote Authentication Dial-In User Service (RADIUS) server
RADIUS is an AAA (authentication, authorization and accounting) protocol for
managing client access to network services. This version of the RADIUS server
is from Lucent Technologies Inc., formerly known as Livingston Enterprises
Inc., and is described by RFC's 2865 to 2869.
.
Some ISP's (commonly modem, DSL, or wireless 802.11 services) require you to
enter a username and password in order to connect to the Internet. Before
access to the network is granted, this information is passed to a Network
Access Server (NAS) device over the link-layer protocol and then to a RADIUS
server over the RADIUS protocol. The RADIUS server checks that the
information is correct using authentication schemes like PAP, CHAP or EAP. If
accepted, the server will then authorize access to the ISP system and select
an IP address, L2TP parameters, etc.
.
RADIUS is also commonly used for accounting purposes so that the users can be
billed accordingly.
Attachment:
signature.asc
Description: Digital signature