Maybe the lease maintenance code compares datetimes in the local timezone against lease expiration times in UTC

[exarkun]

This would lead to a slight miscalculation in when it is necessary to renew leases (early on one side of UTC and tardy on the other).

VoucherStore was recently changed to use UTC-aware datetimes but the lease maintenance code still uses datetime.utcfromtimestamp with reactor.seconds() and the stored lease expiration time as arguments. It's not immediately obvious to me whether these are correct or not.

[meejah]

reactor.seconds() is from the system time? And at least on Linux that is UTC. No idea what windows will do.
(Do we have to use reactor.seconds() there, or can we just use aware_now() as well so we don't have to think about this again?)