> I guess that your next question will be: "then how do I do this using > UW imapd's existing facilities?" > > What you need to do is specify what "this" means: > . use the same database for passwords for all systems? > . negotiate passwords securely? > . negotiate authentication without letting snoops steal passwords? > . etc. > > There is a way to do "this" in UW imapd, but you need to know what > "this" is because doing some "this" prevents you from doing other "this". > > It's like "The Hitchhiker's Guide to the Galaxy", where it is revealed > that the answer to the ultimate question of life, the universe, and > everything is 42. The problem is, nobody knew the question...
Thanks for the explanation. Maybe I can formulate a sensible question now. I would like advice about how to do the following: -use PAM to check usernames and passwords -negotiate passwords securely -negotiate authentication without letting snoops steal passwords (Isn't this the same as the last point? -avoid having to encrypt the the whole session (imaps) Cyrus SASL with SSL/TLS is widely used for client authentication by postfix. I think I'm looking for how to do this with imapd. Mark _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
