aboutsummaryrefslogtreecommitdiffstats
path: root/net/freeradius/pkg-descr
diff options
context:
space:
mode:
authorbrian <brian@FreeBSD.org>2002-05-11 02:59:23 +0800
committerbrian <brian@FreeBSD.org>2002-05-11 02:59:23 +0800
commitdb0f97dae8057cb99f4574ff5378e6688e268922 (patch)
tree5c2c608a4db4d9261a3dcb8e7288e29735e7ef4e /net/freeradius/pkg-descr
parent6a3fde5e2059b5a8ae6594dab65881cc7ddd5bbe (diff)
downloadfreebsd-ports-gnome-db0f97dae8057cb99f4574ff5378e6688e268922.tar.gz
freebsd-ports-gnome-db0f97dae8057cb99f4574ff5378e6688e268922.tar.zst
freebsd-ports-gnome-db0f97dae8057cb99f4574ff5378e6688e268922.zip
Add freeradius, a RADIUS daemon implementation compatible with
livingston radiusd-2.01. This RADIUS implementation implements MS-CHAP authentication whereas most or all of the others don't. Forced into it by: wollman (after removing freeradius-devel)
Diffstat (limited to 'net/freeradius/pkg-descr')
-rw-r--r--net/freeradius/pkg-descr23
1 files changed, 23 insertions, 0 deletions
diff --git a/net/freeradius/pkg-descr b/net/freeradius/pkg-descr
new file mode 100644
index 000000000000..0c9d4b6a0b4b
--- /dev/null
+++ b/net/freeradius/pkg-descr
@@ -0,0 +1,23 @@
+ All code in this server was written from scratch.
+
+ The server is mostly compatible with livingston radiusd-2.01
+ (no menus or s/key support though) but with more feautures, such as:
+
+ o Can limit max. number of simultaneous logins on a per-user basis!
+ o Multiple DEFAULT entries, that can optionally fall-through.
+ o In fact, every entry can fall-through
+ o Deny/permit access based on huntgroup users dials into
+ o Set certain parameters (such as static IP address) based on huntgroup
+ o Extra "hints" file that can select SLIP/PPP/rlogin based on
+ username pattern (Puser or user.ppp is PPP, plain "user" is rlogin etc).
+ o Can execute an external program when user has authenticated (for example
+ to run a sendmail queue).
+ o Can use `$INCLUDE filename' in radiusd.conf, users, and dictionary files
+ o Can act as a proxy server, relaying requests to a remote server
+ o Supports Vendor-Specific attributes
+ o No good documentation at all, just like the original radiusd 1.16!
+
+ Then of course for general RADIUS questions, especially if you are using
+ Livingston / Lucent RABU equipment, there is the portmaster-radius mailing
+ list. Send mail to portmaster-radius-request@livingston.com to find
+ out how to subscribe.