Skip to content

feat(pgp): use preferred hash algorithm for signing instead of hardcoded SHA256#7731

Merged
link2xt merged 1 commit intomainfrom
link2xt/mqqlrqknsszt
Jan 18, 2026
Merged

feat(pgp): use preferred hash algorithm for signing instead of hardcoded SHA256#7731
link2xt merged 1 commit intomainfrom
link2xt/mqqlrqknsszt

Conversation

@link2xt
Copy link
Collaborator

@link2xt link2xt commented Jan 15, 2026

There is no difference for RSA and Ed25519,
the only signing keys that we generate.
The both use SHA256:
https://github.com/rpgp/rpgp/blob/7e3b6c0af21e4a45c2a2dcba67f0b649e0b6e456/src/types/params/public.rs#L231-L234

The only difference is for the possible future PQC signing keys and imported NIST P-512 and NIST P-384 keys.

…ded SHA256

There is no difference for RSA and Ed25519,
the only signing keys that we generate.
The both use SHA256:
<https://github.com/rpgp/rpgp/blob/7e3b6c0af21e4a45c2a2dcba67f0b649e0b6e456/src/types/params/public.rs#L231-L234>

The only difference is for the possible future PQC signing keys
and imported NIST P-512 and NIST P-384 keys.
@link2xt
Copy link
Collaborator Author

link2xt commented Jan 18, 2026

This will make it possible to import P-521 keys: https://support.delta.chat/t/could-you-please-comment-on-this-deltachat-message/4617
To make it clear, this change is just a code cleanup, it does not mean supporting importing keys, especially keys that do not conform to Autocrypt spec. Importing custom keys, especially P-521 which were never used before as they did not work, is not tested, not supported and may result in a broken setup now or in the future.

@link2xt link2xt merged commit 5ff323c into main Jan 18, 2026
30 checks passed
@link2xt link2xt deleted the link2xt/mqqlrqknsszt branch January 18, 2026 03:59
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.

3 participants