Skip to content

fix: ensure public key signatures are not in the past compared to the public key#8397

Open
link2xt wants to merge 1 commit into
mainfrom
link2xt/ultxzussxnkk
Open

fix: ensure public key signatures are not in the past compared to the public key#8397
link2xt wants to merge 1 commit into
mainfrom
link2xt/ultxzussxnkk

Conversation

@link2xt

@link2xt link2xt commented Jul 2, 2026

Copy link
Copy Markdown
Collaborator

We use the timestamp of the latest transport modification as the timestamp of the Direct Key Signature.
However, first transport is created before the public key and existing transports may even have zero timestamp if they were created before migration 142.

For interoperability with Sequoia-PGP,
make sure signatures always have a timestamp
that is not in the past compared to the timestamp
of the primary key.

Closes #8383

… public key

We use the timestamp of the latest transport modification
as the timestamp of the Direct Key Signature.
However, first transport is created before the public key
and existing transports may even have zero timestamp
if they were created before migration 142.

For interoperability with Sequoia-PGP,
make sure signatures always have a timestamp
that is not in the past compared to the timestamp
of the primary key.
@link2xt link2xt force-pushed the link2xt/ultxzussxnkk branch from 9c54d03 to 7d60e17 Compare July 2, 2026 00:45
@link2xt link2xt marked this pull request as ready for review July 2, 2026 03:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Delta Chat keydata contains inconsistent timestamps

1 participant