atom feed18 messages in net.sourceforge.lists.courier-users[courier-users] Best unix distributed...
FromSent OnAttachments
Les StottMar 6, 2001 7:04 pm 
Sam VarshavchikMar 6, 2001 7:48 pm 
Patrick PriceMar 7, 2001 12:01 pm 
Leonid AndreevMar 7, 2001 12:28 pm 
Leonid AndreevMar 7, 2001 12:38 pm 
Brad DameronMar 7, 2001 1:01 pm 
Brad DameronMar 7, 2001 1:20 pm 
Leonid AndreevMar 7, 2001 1:49 pm 
Nerijus BaliunasMar 7, 2001 3:02 pm 
Ben BeuchlerMar 7, 2001 3:25 pm 
Sam VarshavchikMar 7, 2001 3:40 pm 
Nerijus BaliunasMar 7, 2001 4:37 pm 
Nerijus BaliunasMar 7, 2001 4:43 pm 
Sam VarshavchikMar 7, 2001 5:12 pm 
Patrick PriceMar 7, 2001 6:02 pm 
Patrick PriceMar 7, 2001 6:04 pm 
Clint BullockMar 12, 2001 8:23 am 
Georg LutzMar 12, 2001 3:29 pm 
Subject:[courier-users] Best unix distributed authentication method?
From:Patrick Price (sysa@moment.net)
Date:Mar 7, 2001 12:01:51 pm
List:net.sourceforge.lists.courier-users

This is a little off topic of Courier per se ....

If someone can point me in the right direction for FAQ's or HOWTO's ...

Presently I use NIS for unix username/password distribution, Radius using MySQL, and some authuserdb stuff for Courier.

What I need to know is, what good is LDAP? PAM? And which combination of these is best for a fault-tolerant, distributed password system which would support unix logins, ftp, radius, Courier, etc?

Key words being fault tolerant, distributed, and one administrative interface? Am I asking the impossible?

Here's what I have to deal with now:

1: /etc/passwd for unix logins, ftp 2: MySql for radius 3: authuserdb for virtual users for Courier 4: Rely on NIS to share /etc/passwd for multiple unix boxes

The administration of these is driving me crazy, and if NIS goes down I'm screwed.

Thanks for any input!