-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Qubes templates build command gpg error: Signature by [key] was created after the --not-after date.
#8520
Comments
Downloaded the text and verified.
How to reproduce the issue? Maybe a timezone issue... |
I'd rather guess it's Whonix's time randomization - the signature has timestamp of 4:35, but was posted on github at 4:33, which suggests time travel... |
Possible to add a sanity test to the
If that's the case, that shouldn't matter? |
Gpg signature has timestamp when it was made, signatures made in the future are invalid (similar to certificates issues in the future - we see that from time to time on Whonix and LetsEncrypt certificates, but also on Debian release files for Debian fasttrack - this also fails semi-frequently due to wrong time in Whonix...). Gpg in default settings may not verify it, but we use sequoia which is much stricter. |
Signature by [key] was created after the --not-after date.
Is there anything to be done on the Qubes side? This seems like a Whonix problem that needs to be worked around in Whonix. |
Possible to add a sanity test to the |
@adrelanos this happened again
What should it do? VM in which you run template-github has wrong time so checking against local time is pointless. |
I'm going to post new command now similar to retry the build. |
Only the remote side could check it and reject.
https://forums.whonix.org/t/boot-clock-randomization-bootclockrandomization/2200/17
For Qubes Templates only that was reduced to +/-1sec indeed already.
Opt-out is easy and documented here:
|
quote QubesOS/updates-status#566 (comment) @fepitre
I didn't touch my gpg config and I don't mix other keys into that VM. So this issue is surprising.
The text was updated successfully, but these errors were encountered: