Neal H. Walfield

> > Is a "key master" the entity that controls the key? > I think I was using the word _certificate_ inconsistently, but mostly in the same way you are....

@pmatilai, unfortunately, I think you're right. Where should we discuss how to implement the merge / update operation?

Ok, thanks for the clarification. From my perspective, there is no way to generate a version number for an OpenPGP certificate. This is because an OpenPGP certificate is composed of...

I'd really prefer that we merge the existing certificate with the new certificate. This is particularly important as gpg strips old self signatures when exporting certificates. One consequence of replacing...

> Fixed by #3083 (but not in rpm-sequoia yet) I'll find some time to add this in the near future. Thanks everyone who made this possible!

Is this issue the right place to talk about an updated API for the PGP backend, [as mentioned elsewhere](https://github.com/rpm-software-management/rpm/issues/1978#issuecomment-1081839784), or would it be better to open a different issue for...

@j-mracek Thanks for following up! Can you elaborate on the requirements? (Or perhaps point me to a document or issue or...)

To elaborate on what @teythoon said: Adding OpenSSL support shouldn't be a major undertaking. Sequoia already supports three cryptographic libraries (Nettle, Rust Crypto and Windows CNG), so the existing abstractions...

> for minimal container images and such people are pushing quite hard to minimize the dependencies and that includes consolidating on a single crypto library to the extent possible. I...

Thanks for following up, that is helpful. Could you also comment on why using Sequoia would increase the cost of the installation requirements too much.