Package: radiusd-livingston Version: N/A Severity: normal Tags: patch
Dear Debian maintainer, On Sunday, May 06, 2007, I notified you of the beginning of a review process concerning debconf templates for radiusd-livingston. The debian-l10n-english contributors have now reviewed these templates, and the proposed changes are attached to this bug report. Please review the suggested changes are suggested, and if you have any objections, let me know in the next 3 days. Please try to avoid uploading radiusd-livingston with these changes right now. The second phase of this process will begin on Sunday, May 27, 2007, when I will coordinate updates to translations of debconf templates. The existing translators will be notified of the changes: they will receive an updated PO file for their language. Simultaneously, a general call for new translations will be sent to the debian-i18n mailing list. Both these calls for translations will request updates to be sent as individual bug reports. That will probably trigger a lot of bug reports against your package, but these should be easier to deal with. The call for translation updates and new translations will run until Friday, June 08, 2007. Please avoid uploading a package with fixed or changed debconf templates and/or translation updates in the meantime. Of course, other changes are safe. On Saturday, June 09, 2007, I will contact you again and will send a final patch summarizing all the updates (changes to debconf templates, updates to debconf translations and new debconf translations). Again, thanks for your attention and cooperation. Kevin -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash -- Kevin Coyner GnuPG key: 1024D/8CE11941
*** warning *** Template: radiusd-livingston/configure_clients Type: note _Description: Mandatory configuration of clients for the RADIUS server Please copy the example file /usr/share/doc/radiusd-livingston/examples/clients to /etc/radiusd-livingston/clients and edit it, adding an entry for each client system. Template: radiusd-livingston/configure_users Type: note _Description: Mandatory configuration of users for the RADIUS server Please copy the example file /usr/share/doc/radiusd-livingston/examples/users to /etc/radiusd-livingston/users and edit it, adding an entry for each user account.
Source: radiusd-livingston
Section: net
Priority: optional
Maintainer: Paul Martin <[EMAIL PROTECTED]>
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, and is described by RFCs 2865 to
2869. This version of the RADIUS server is from Lucent Technologies Inc.,
formerly known as Livingston Enterprises Inc.
.
Some Internet Service Providers (ISPs) require a username and password to be
given on connection. 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's 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.
signature.asc
Description: Digital signature
