[Rpm-maint] [rpm-software-management/rpm] Begin decoupling rpm's crypto API's from PGP (PR #1937)

[Panu Matilainen]

@pmatilai commented on this pull request.



> +
+typedef rpmFlags rpmDigestFlags;
+
+/** \ingroup rpmcrypto
+ * Perform cryptography initialization.
+ * It must be called before any cryptography can be used within rpm.
+ * It's not normally necessary to call it directly as it's called in
+ * general rpm initialization routines.
+ * @return		0 on success, -1 on failure
+ */
+int rpmInitCrypto(void);
+
+/** \ingroup rpmcrypto
+ * Shutdown cryptography
+ */
+int rpmFreeCrypto(void);

Well that's the main reason. Rpm being mostly a library ends up in other people's projects, and some care more about the clean-at-exit status than others. Plus there may be situations where you want to explicitly shut down the crypto before eg forking a process, NSS was infamously picky about these situations.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1937#discussion_r814526779
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/pull/1937/review/893336982 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20220224/906b896a/attachment.html>