Teco Boot <[email protected]> wrote: > This started with a need for somewhat accurate system time for > certificate validation, right? I have to deal with stuff lacking a RTC > battery. I save system time every now and then in flash. During > startup, clock jumps forward to RTC when warm start occurs (main power > was not interrupted) or to saved system time when a cold boot > occurs. When clock is behind, it jumps forwards when NTP syncs. My > certificates do not expire during "powered off, on the shelf".
I was looking for a write up that explained this, that had some thoughts about threats mitigated, and threats that still exist. The reason for this, is mostly for Security Considerations, to argue that even though devices may not have battery-backed RTCs, they could still have reasonable time. -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
