[IDS] What to use for "system clock was changed" event?

[IDS] What to use for "system clock was changed" event?

Ira McDonald blueroofmusic at gmail.com
Tue Dec 20 00:35:20 UTC 2011


Hi Joe and Mike,

Nope - the clock could have been manually or automatically
changed (e.g., to correct for drift while off the Internet) without
reconfiguring the NAC TimeSource value.

And calling that a ConfigChanged event is stretching and pretty
obscure, IMHO.

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto:blueroofmusic at gmail.com
Winter  579 Park Place  Saline, MI  48176  734-944-0094
Summer  PO Box 221  Grand Marais, MI 49839  906-494-2434



On Mon, Dec 19, 2011 at 6:36 PM, Murdock, Joe <jmurdock at sharplabs.com>wrote:

> I think this message would have triggered off of a change in the
> TimeSource NAC attribute to indicate that someone reconfigured the time
> source used for security and encryption****
>
> ** **
>
> *From:* ids-bounces at pwg.org [mailto:ids-bounces at pwg.org] *On Behalf Of *Michael
> Sweet
> *Sent:* Monday, December 19, 2011 3:27 PM
> *To:* IDS Work Group
> *Subject:* [IDS] What to use for "system clock was changed" event?****
>
> ** **
>
> All,****
>
> ** **
>
> As I was going through the last of the IDS Log changes I need, I noticed
> in my notes that someone asked for an example of a time-change message
> (i.e. system clock was changed), but we don't have something for this in
> IDS Model.****
>
> ** **
>
> Thoughts?****
>
> ** **
>
> ________________________________________________________________________**
> **
>
> Michael Sweet, Senior Printing System Engineer, PWG Chair****
>
> ** **
>
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean. ****
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
>
> _______________________________________________
> ids mailing list
> ids at pwg.org
> https://www.pwg.org/mailman/listinfo/ids
>
>

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ids/attachments/20111219/7af07ba2/attachment-0001.html>


More information about the ids mailing list