[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[LCFC] templates://radiusd-livingston/{templates}



This is the last call for comments for the review of debconf
templates for radiusd-livingston.

The reviewed templates will be sent on Thursday, May 24, 2007 to the package
maintainer as a bug report and a mail will be sent to this list with
"[BTS]" as a subject tag.


-- 
Kevin Coyner  GnuPG key: 1024D/8CE11941
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 <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, 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.

Attachment: signature.asc
Description: Digital signature


Reply to: