RE: authentication mechanisms

"Sasha Romanosky" <[email protected]>
Newsgroups gmane.org.user-groups.linux.pdxlug
Message-ID <001a01c41126$35847880$6501a8c0@LAPTOP>
Kevin, 

You might find useful suggestions and emails from the webappsec
(http://www.securityfocus.com/subscribe?listname=107) mailing list.

One thread in particular that we discussed was regarding authentication
and authorization. This speaks more to web app authentication, but the
issues of authenticating over a network still apply. You might find some
of this useful:
http://lists.virus.org/webappsec-0309/msg00149.html

Cheers,
Sasha

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Kevin Williams
> Sent: Tuesday, March 23, 2004 10:28 AM
> To: PDXLUG, a Portland Linux user group
> Subject: [PDXLUG] authentication mechanisms
> 
> 
> All,
> 
> I'm in the process of improving my Linux administration 
> skills (well actually create them) and am trying to 
> understand the different authentication mechanisms that are 
> available (kerberos, standard UNIX, LDAP, PAM, SASL, shadow 
> passwords, etc...), when to implement these different 
> mechanisms, and what their advantages/disadvantages are.  
> Does anyone have any recommendations for where to start in 
> this learning process (books, links, etc...)?
> 
> My goal is the following: Have a server that hosts 
> authentication information for both windows and linux 
> clients.  This authentication information would be used for 
> both client computer login (act as a windows domain) and 
> email (IMAP and SMTP).
> 
> Thanks in advance,
> 
> Kevin Williams
> _______________________________________________
> PDXLUG mailing list
> [email protected]
> http://pdxlug.org/mailman/listinfo/pdxlug
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.