On Mon 2024-09-09 15:13:07 +0200, Werner Koch via Gnupg-users wrote: > Advertisement for other applications, like a Python wrapper around a > long standing command line API (going all the way back to pgp 2), is > thus off-topic.
Jakob specifically asked how he could use GnuPG while relying on the return code. I pointed to some tooling that is designed to do that specifically, not to avoid the use of GnuPG. In particular, the command line API for GnuPG tools is itself quite idiosyncratic, as "long standing" CLIs tend to be. > It feels more like a SEO strategy than as helpful information. Please > don't confuse users; search engines already deliver too much > misinformation on best gpg practices. I agree that there is a lot of misinformation in the wild about how to "best" use gpg. I think if the GnuPG interface lent itself to the type of straightforward system integration like Jakob was asking for, there would probably be fewer workarounds, not-quite-complete shell scripts, or ambitious-yet-flawed guidance floating around about the project. Tooling that deliberately transforms GnuPG's idiosyncratic interface into a simpler, easier-to-integrate DWIM syntax/semantics is intended as a contribution to the GnuPG project, so that people who want to rely on GnuPG can do so safely. Sorry if it didn't read that way from the outset. All the best, --dkg
signature.asc
Description: PGP signature
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
