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

RFE: add support for SHA-3 #3436

Open
pmatilai opened this issue Nov 8, 2024 · 3 comments
Open

RFE: add support for SHA-3 #3436

pmatilai opened this issue Nov 8, 2024 · 3 comments
Labels
crypto Signatures, keys, hashes and their verification RFE

Comments

@pmatilai
Copy link
Member

pmatilai commented Nov 8, 2024

The post-quantum signatures are all SHA-3 based, rpm needs to recognize them. As the actual crypto comes from rpm-sequoia or rpmpgp_legacy, the rpm side of this is little more than adding a couple of enums but it still needs to be done.

Besides PQ signatures, we'll want to be able to move to stronger digest for our own purposes too, sooner or later.

@pmatilai pmatilai added RFE crypto Signatures, keys, hashes and their verification labels Nov 8, 2024
@pmatilai pmatilai added this to RPM Nov 8, 2024
@github-project-automation github-project-automation bot moved this to Backlog in RPM Nov 8, 2024
@pmatilai
Copy link
Member Author

pmatilai commented Nov 8, 2024

AFAICS SHA-3 in rpm-sequoia depends on the crypto-refresh branch to land in main Sequoia first.

@nwalfield
Copy link
Contributor

That's correct. We plan to add support for 9580 to sequoia-openpgp 2.0, which is due out early next year. Note: 2.0 will not include support for PQC, because it is not yet standardized.

@pmatilai
Copy link
Member Author

pmatilai commented Nov 8, 2024

Nothing in rpm v6 depends on SHA-3 so this isn't timing critical for us, it's more of a "HDTV-ready" type of thing 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crypto Signatures, keys, hashes and their verification RFE
Projects
Status: Backlog
Development

No branches or pull requests

2 participants