On Sun, 3 Jul 2016 15:35, d...@fifthhorseman.net said:
> report. If GnuPG gave an error when asked to set timestamps outside of
> its representable range, would that be sufficient to close this bug?
Which is actually problematic because on many system time_t is signed
and wraps in 2038. Thus
On Sat 2016-07-02 15:43:54 -0400, Luke Faraone wrote:
> Creating a key that expires in 89 years correctly sets an expiry of 2105, but
> attempting to set an expiry of 90 years or greater results in an expirty date
> that wraps around to 1970.
>
> Curiously, the time on such wrapped-around expiries
Luke Faraone wrote:
> Creating a key that expires in 89 years correctly sets an expiry of 2105, but
> attempting to set an expiry of 90 years or greater results in an expirty date
> that wraps around to 1970.
>
> Curiously, the time on such wrapped-around expiries is always 13:09:41.
This is the
Package: gnupg2
Version: 2.1.11-7
Severity: normal
Creating a key that expires in 89 years correctly sets an expiry of 2105, but
attempting to set an expiry of 90 years or greater results in an expirty date
that wraps around to 1970.
Curiously, the time on such wrapped-around expiries is always
4 matches
Mail list logo
