Hi, maybe it was already answered.Not long ago Thunderbird switched from using installed GPG to its own implementation inside. I think I have found the library part and it seems to be in C++, which should be much more easier to integrate than rust libraries.
I think the project link is: https://github.com/rnpgp/rnpWouldn't it solve the problems cause in more compatible way? Is has relatively recent release, so it does not seem abandoned. Is there a specific reason, why is a Rust implementation chosen instead? I like Rust language, but its integration into a core system component does not seem easy.
Cheers, Petr On 20. 10. 22 11:03, Miro Hrončok wrote:
On 10. 10. 22 16:32, Ben Cotton wrote:For the last 20 years or so, RPM has used a home-grown OpenPGP parser for dealing with keys and signatures. That parser is rather infamous for its limitations and flaws, and especially in recent years has proven a significant burden to RPM development. In order to improve security and free developer resources for dealing with RPM's "core business" instead, RPM upstream is in the process of deprecating the internal parser in favor of [https://sequoia-pgp.org/ ; Sequoia PGP] based solution written in Rust. At this point the change is mostly invisible in normal daily use.Which of the following will happen: 1) rpm will gain ExclusiveArch: %{rust_arches}2) we will stop requiring the above in Rust packages, as Rust is 100% available3) rpm will %ifarch %{rust_arches} this change 4) something else (what?)IMHO if we do 1) we could as well do 2) because without rpm, we won't be able to build rpms. 3) seems somewhat tedious for no good reason.
-- Petr Menšík Software Engineer, RHEL Red Hat, http://www.redhat.com/ PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
Attachment:
OpenPGP_0x4931CA5B6C9FC5CB.asc
Description: OpenPGP public key
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
