tpop3d-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [tpop3d-discuss] tpop3d v1.4.1pre4


From: Prune
Subject: Re: [tpop3d-discuss] tpop3d v1.4.1pre4
Date: Mon, 25 Feb 2002 10:25:21 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2

Hi,

big big problem :
I can't find any README.auth_ldap
In fact, it should be my duty....
Would you like me to do it ? (with my poor english ?)

Cheers,

Prune (still happy)

Chris Lightfoot wrote:

 http://www.ex-parrot.com/~chris/tpop3d/tpop3d-1.4.1pre4.tar.gz

This version incorporates auth-ldap and a fix to the BSD
metadata cache code. In order to cleanly integrate the new
authentication code, there has been a slight semantic
change to the operation of authentication in tpop3d. This
is explained more fully in the tpop3d.conf man page in the
new distribution, but basically--

   - previously, users had a `username' which under some
     circumstances would be interpreted as a
     address@hidden string and used for
     authentication; it was up to individual
     authenticators to do this parsing.

   - If append-domain was switched on, then a username
     without a separator might be passed to
     authenticators with an @domain suffix.

   - Now, the concept of a local-part separate from a
     username is maintained throughout the code.
     `Username' always refers to the string which the
     client supplied.

   - If a client supplies a string with no separator in
     it, and append-domain is not switched on, then no
     local-part is generated and only a username and
     domain are passed to authenticators.

   - If append-domain is switched on, then the username
     is also used as the local-part when authentication
     is retried.

   - If there is a separator in the username, then the
     local-part and domain specified replace those
     derived by other means.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]