0

I'm trying to sign a LibreOffice document blah blah... So, I created a key and signed my document, but when I reload it, LO insists that the "certificate is not yet valid", and apparently won't be for several hours.

Poking around in gpg, I see that the key's issue date is in fact... tomorrow. Specifically, it looks like it is in the future by my UTC offset. (For example, say it is 10-01 23:00 local time, 10-02 05:00 UTC time. The key shows 10-02 05:00 as the creation time... with no time zone. And at least LO appears to read that as local time, such that the key appears to have been created in the future by however many hours my local time is behind UTC. I can only assume someone from e.g. India would have the opposite problem, although a key being created in the past isn't nearly as problematic.)

Now... I could just wait, but I'd like to understand why this is happening and what I can do about it. Why is GPG creating keys in a manner that their issue date is in the future, and how do I fix it? (Note, this isn't a problem with my clock; my clock has the correct time.)

Improve this question
6
  • Meanwhile, faketime seems to be an effective work-around. Shout-out to superuser.com/questions/1045904. Commented Oct 1 at 5:33
  • 1
    I'm sorry, but I don't understand the phrase "it looks like it is in the future by my UTC offset". So ... what was your system time and timezone, when you created the key, what is the issue date, ..... I'm afraid there is still information missing that might help diagnose the problem. Commented Oct 6 at 15:08
  • @AdminBee, I mean, I created my key at e.g. 10-01 23:00 local (which is, say, 05:00 UTC), and the key shows up as being created at 10-02 05:00. And applications (LibreOffice in particular) are upset because it "isn't" 10-02 05:00 local time yet. Commented Oct 6 at 18:56
  • 1
    My knee jerk reaction to this would be to assume the problen is the other way around: that gpg is behaving correctly and somehow LibreOffice is misinterpreting things by reading a timestamp that is intentionally UTC as if it's in local time. I say this without looking into the problem very deeply. Commented Oct 6 at 22:45
  • @PhilipCouling, possible, but inspecting the key in GPG shows the same questionable creation time, with no indication that it's in UTC. Commented Oct 7 at 4:01

0

Reset to default

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.