On 09/02/2015 11:18 AM, Dennis Gilmore wrote:
On Wednesday, September 02, 2015 04:45:33 PM Till Maas wrote:
On Tue, Sep 01, 2015 at 01:38:21PM -0500, Dennis Gilmore wrote:
Without a battery backed RTC its really not that useful. Picture 6 or 10
months after a release, does it matter if the time is half a year to a
year
off or 35 years off?
If a system needs to use something TLS-protected, then the system clock
must not be too much off because a certificate might not be valid
otherwise. At least in debian there is also a fake hwclock package that
reduces the offset to the time that passed since the system was last
booted:
Sure, but is there uses for TLS without the network having come up? at which
point chronyd would have set the time correctly.
I do a lot of work in IoT, much of it Zigbee or Zwave. But would also
like to get into Bacnet.
We push real hard on secure communications within the home. So as I
said, the home controller is the web server with the cert and it is on
UPS and survived the power flux and still has the correct time. The
furnace controller went off line until it was restarted on the switch to
the backup home generator. Now the furnace controller has bad time in
connecting to the home controller over TLS.
i can go on and on. Yes these are all edge cases, but you have to
design for them.
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm
