On Sat, Feb 19, 2000 at 03:29:40PM +0100, Fredrik Liljegren wrote:
> > > For reasons stated below, I think of adding pam to cvs. My
> ...
>
> > If you're going to generalize the authentication mechanism, I strongly
> > recommend generalizing it in the direction of SASL rather
> > than just PAM.
> > They're not opposing ideas; in fact, PAM becomes considerably
> > more useful
> > in more circumstances if you have SASL as well.
>
> I don't even know what SASL is.. I have lloked into PAM and the Linux-PAM
> Application Developers' Guide, and it doesn't seem that hard to implement.
> Would SASL be as easy?
Simple Authentication and Security Layer:
http://asg.web.cmu.edu/sasl/. I don't know much about it other than what
I had to learn to make Cyrus IMAPD work. It certainly looks like the way
to go for this type of thing.
The thing that actually stopped me from using PAM with CVS was the
fact that the client stores the pserver password in plain text. I didn't
want everyone's NT domain passwords sitting in plain text on their hard
drives, so I kept the CVS logins separate.
--
Lachlan O'Dea <mailto:[EMAIL PROTECTED]> Computer Associates Pty Ltd
Webmaster Vet - Anti-Virus Software
http://www.vet.com.au/
"With our combined strength, we can end this destructive
conflict and bring order to the galaxy." - Darth Vader
