>From the issue:
<<<
As far as I can see, the only timestamp used is expiration_date in the
ServerConfiguration (apart from X.509 validity checks which require
synchronised clocks). This is defined as seconds since UNIX epoch, and
will overflow sooner than later. Maybe either use a relative
On Mon, Nov 23, 2015 at 10:28:41AM -0800, Martin Thomson wrote:
> >From the issue:
>
> I don't want to see this change to a relative time. That will mess
> with our ability to create ServerConfiguration objects that live
> outside of the handshake.
>
> I have no real objection to expanding this
