Timing out the passwords is simple ( I think ) I would store the time when the entry is added and force a reauth if the password has been cached longer than a timeout (for example one hour ). That forces a reauth at least every timeout period of time. If an entry isn't in the cache (or if it is different the entry would be removed and ) a reauth would be forced. Every successfull auth would be added to the cache.
Jure Pecar wrote: > > On Thu, 09 Jan 2003 13:45:41 -0600 > Paul M Fleming <[EMAIL PROTECTED]> wrote: > > > Related to this thread... I am considering writing a generic cache layer > > into saslauthd to lessen the load on the backend auth mechanism. My idea > > is to implement a hash table in shared memory and use that to cache the > > userid,password etc with a timeout. This should lighten the load .. > > Comments? Ideas? Suggestions?? > > That would be handy, sure. Just think of some smart way to timeout the > cached passwords ... or some feedback mechanism that the password has > recently changed ... > > -- > > Jure Pecar