Skip to content
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

Make sure that changing of the key expiration works for SHA-1 selfsigs and updates hash to the stronger one. #1810

Open
ni4 opened this issue Apr 28, 2022 · 3 comments · May be fixed by #2295
Assignees
Milestone

Comments

@ni4
Copy link
Contributor

ni4 commented Apr 28, 2022

Description

It doesn't seem to work in this way for now.

@ni4 ni4 added this to the v0.17.0 milestone Apr 28, 2022
@ni4 ni4 removed this from the v0.17.0 milestone Feb 27, 2023
@ni4 ni4 added this to the v0.18.0 milestone Jun 12, 2023
@ni4 ni4 self-assigned this Jun 12, 2023
@kaie
Copy link
Contributor

kaie commented May 14, 2024

It would be good to make this a higher priority. It's been two years, and it seems important to finally get rid of SHA1 in this scenario.
cc @ronaldtse

@kaie
Copy link
Contributor

kaie commented May 14, 2024

Tracker on the Thunderbird side:
https://bugzilla.mozilla.org/show_bug.cgi?id=1837889

@dkg
Copy link
Contributor

dkg commented May 14, 2024

This seems similar to the proposal for a sop update-key. It would be great if rnp could implement sop (#1760), and if you do, please consider commenting on that proposal!

@ni4 ni4 removed their assignment Nov 24, 2024
@desvxx desvxx self-assigned this Nov 26, 2024
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 a pull request may close this issue.

4 participants