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

Re: Last login incorrect

Well, to be meaningful it would need to be shared among all the  
servers, which would mean a "reverse channel" capability for ipropd.   
Don't know about Microsoft, but MIT doesn't do that.  The info is  
inherently local a single KDC, and would probably get wiped out by the  
DB replication process anyway.

In other words it's a moderately hard problem, especially if you want  
the info to be useful.

If you want to do something useful that uses that kind of information  
then you can read the log files and pull it out.  We have log readers  
that send info to collator that temporarily disables accounts with too  
many failed authentications for example.

On May 29, 2008, at 11:01 AM, Robert C. Sheets wrote:

> On Thu, May 29, 2008 at 10:55:25AM -0700, Henry B. Hotz wrote:
>> Not implemented.  Output for MIT display compatibility.  (Unless Love
>> has added something I don't know about.)
> OK, good to know. Is this planned for some future version, or is it
> deliberately not implemented?
> Thanks,
> -- 
> Robert C. Sheets
> Picosecond Software

The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
Henry.B.Hotz@jpl.nasa.gov, or hbhotz@oxy.edu