Hi, Caskey. On Tue, 11 Mar 2003, Caskey Dickson wrote: >On Tue, Mar 11, 2003 at 11:16:24AM +0100, Andreas Aardal Hanssen wrote: >> Then I understand that you agree that reading from 0 is equally simple. >> Reading from 3 is just a hack that qmail/checkpassword uses, because qmail >> has hijacked 0, 1 and 2 for other purposes. It's the year 2003 now, and I >> don't want the authentication API to expect fd 3 to be free for use. >> The stub bincimap-auth-checkpassword will still write to checkpassword's >Binc's authenticator returns after having authenticated but qmail's pop >server does not, its child takes over the pop session on stdin/stdout. >For daemons that use stdin/stdout to communicate with the client, those >two handles are not available. >Switching to stdin and abandoning the checkpassword protocol is fine, >but doing so means that we cut ourselves off from every one of the >dozens of checkpassword implementations available right now.
No! I think you totally misunderstand. Binc launches bincimap-auth-checkpassword. Binc talks to bincimap-auth-checkpassword. bincimap-auth-checkpassword talks to checkpassword. We are _not_ changing bincimap-auth-checkpassword! Binc currently uses the environment variables BINC_USERID and BINC_PASSWD to talk to its authenticator. bincimap-auth-checkpassword is an authenticator that also functions as a stub for checkpassword. We are removing the environment communication and replacing it with netstrings - and we will use stdin and stdout for this. So instead of used BINC_USERID and BINC_PASSWD, we will use 7:andreas,8:password, And Binc will write this to it's authenticator's stdin. That's all. Andy -- Andreas Aardal Hanssen | http://www.andreas.hanssen.name/gpg Author of Binc IMAP | Nil desperandum
