Environment

redhat 7.2, gpg 1.0.6

Description

you bastards. why on earth would you deny the import of a perfectly valid pgp key on the grounds of it's creation date being set in the future? that's just CRUEL. haven't you ever, say, been in australia, created a key, and tried to import it to a machine in the US? is this such an outlandish idea? AM I CRAZY??????????

Fix

I can't decide whether you are crazy ;-). The timestamps are stored in UTC and thus your argument is void. Well, there are still folks today around where the clock has not been set correctly which leads to all kinds of problems (I especially like mails with a wrong date, so that I won't notice them at the expected place in my mail folders).

The RIPE once encountered a similar problem with a very few keys and thus I added the option --ignore-time-conflict. You may want to put this into your ~/,gnupg/gpg.conf if you have reasons not to fix your clocks.