> It won't. courier-authlib takes a userid and a password, and tries to
> authenticate it via PAM. Anything other than plain userid/password
> authentication won't work.
Right -- I was thinking about that from a theoretical level -- the PAM
API, which I haven't looked greatly at, supports those interactive type of
logins (possibly as an argument to a method, etc.)
Not sure if PAM is a published standard, but:
Hypothetically, wouldn't that then imply that any PAM-compatiable-consumer
code would have to support it to be compatible?
The whole layered API stacking here is ugly. I'm not looking forward to
it.
Getting away from SASL (and to some extent, PAM) is explicitly why we run
Courier :)
~BAS
>
>
l8*
-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
http://www.spiritual-machines.org/
"Show me a young conservative and I'll show you someone with no heart.
Show me an old liberal and I'll show you someone with no brains."
~ Winston Churchill
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
