RE: syslog implementations etc.

[by way of "Chris M. Lonvick" <[EMAIL PROTECTED]>]

 >>>>> "Alex" == Alex Brown <[EMAIL PROTECTED]> writes:

Alex> [EMAIL PROTECTED] wrote:  "Time synchronization is _definitely_ outside
Alex> the scope of a logging protocol."

Actually, _I_ said that.

Alex> I agree that there should be as few protocol dependencies in the solutions
Alex> chosen as possible, esp. at the client, but it is important to identify
Alex> security-related information dependencies that they might indicate.   For
Alex> example, the log timestamp not only confirms serialization of events, but
Alex> gives them a quantifiable relationship in time.  It's well worth
Alex> identifying needs for accuracy and trust in a time source at the logging
Alex> system.

Which is why I suggested propogating the originator's timestamp in the log
message. This solves the problem without exceeding our scope. Whether you
want to include intermediate hop timestamps as well is a topic for discussion.

Cross-machine time synchronization is NTP's job, not ours.

-- 
Carson Gaspar -- [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.cs.columbia.edu/~carson/home.html
Queen Trapped in a Butch Body