Repository navigation
Autocrypt 2 - #8318
Draft
link2xt wants to merge 1 commit into
Draft
Autocrypt 2#8318link2xt wants to merge 1 commit into
link2xt wants to merge 1 commit into
Conversation
link2xt
force-pushed
the
link2xt/autocrypt2
branch
2 times, most recently
from
June 17, 2026 17:22
f08a85f to
0a0f770
Compare
link2xt
changed the base branch from
main
to
link2xt/pgp-subkey-selection-merging-minimization
June 17, 2026 17:30
link2xt
force-pushed
the
link2xt/autocrypt2
branch
from
June 17, 2026 17:37
0a0f770 to
bb1cc58
Compare
link2xt
force-pushed
the
link2xt/autocrypt2
branch
2 times, most recently
from
June 24, 2026 04:58
1e1ff2d to
11e9ac7
Compare
link2xt
force-pushed
the
link2xt/autocrypt2
branch
from
June 24, 2026 14:01
11e9ac7 to
257f2a7
Compare
link2xt
force-pushed
the
link2xt/autocrypt2
branch
from
July 1, 2026 12:14
257f2a7 to
45c0a37
Compare
link2xt
force-pushed
the
link2xt/autocrypt2
branch
from
September 24, 2026 11:47
45c0a37 to
598a63a
Compare
link2xt
added this pull request to stack #8745
September 24, 2026 11:49
link2xt
force-pushed
the
link2xt/autocrypt2
branch
from
October 7, 2026 16:35
598a63a to
43e64cc
Compare
link2xt
force-pushed
the
link2xt/autocrypt2
branch
from
October 7, 2026 19:24
43e64cc to
7fdc984
Compare
link2xt
force-pushed
the
link2xt/autocrypt2
branch
from
October 8, 2026 16:09
7fdc984 to
3d0eb39
Compare
link2xt
force-pushed
the
link2xt/autocrypt2
branch
2 times, most recently
from
October 8, 2026 16:20
c26f26d to
f34b814
Compare
link2xt
force-pushed
the
link2xt/autocrypt2
branch
from
October 8, 2026 16:35
f34b814 to
fc3b22f
Compare
link2xt
force-pushed
the
link2xt/autocrypt2
branch
from
October 8, 2026 17:10
fc3b22f to
ce8aba6
Compare
link2xt
force-pushed
the
link2xt/autocrypt2
branch
from
October 10, 2026 21:01
ce8aba6 to
6e0434c
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #8317
Closes #8224. For Autocrypt 2 keys we set creation timestamp of the primary key and fallback subkey to 0. These timestamps cannot be changed. Direct key signature we already recreate before deriving the public key, and fallback subkey signature we can also recreate each time. For rotating subkey there is no problem as it will be recreated each 10 days. Autocrypt 1 key generation is not changed, we will likely want to remove it eventually anyway once Autocrypt 2 key generation is enabled.
There is a reference Rust implementation in https://codeberg.org/autocrypt2/autocrypt-v2-cert/ as well, we want to keep it in sync but i'm not using it directly as we don't need deterministic key generation, have different error handling, need to set timestamps to 0, and there going to still be changes to the specification. It would be great to merge the codebases and turn this into a single implementation properly published as a crate.