Page MenuHome GnuPG

Key import on a machine with date moved back
Open, LowPublic

Description

I'm opening this issue so that this bug report doesn't get lost.

On Fri 2016-12-02 06:43:19 -0500, A.L.E.C wrote:

So, the question is how can we improve that? In general I'd like to
import the key-pair as if there were no time issues. Maybe there's a
command line argument to ignore them?

Or maybe it's already fixed/implemented in 2.1?

2.1 does have --ignore-time-conflict, but i agree with you that it might
make more sense to tolerate a "typical" clock skew of a few seconds or
minutes by default.

Perhaps it'd make more sense to have a "tolerate-clock-skew" option that
takes a time value, with some sensible default like 10min.

--dkg

Event Timeline

neal set External Link to https://lists.gnupg.org/pipermail/gnupg-devel/2016-December/032262.html.Jan 6 2017, 9:25 PM
neal added projects: gnupg, Bug Report.
neal added subscribers: dkg, werner, neal.