Re: import key failure, apparent bug
Sam James via Gnupg-users <[email protected]> Sat, 30 May 2026 08:55:25 +0100
| Newsgroups | gmane.comp.encryption.gpg.user |
|---|---|
| Organization | Gentoo |
| Message-ID | <[email protected]> |
--===============4050969435964027806== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" --=-=-= Content-Type: text/plain marqueandreprisal--- via Gnupg-users <[email protected]> writes: > Yeah like I said GnuPG you really shouldn't rely on other guys > libs. GnuPG is not a good fit for me because they do so it is nothing > but a buggy frontend with unreliable cryptography. Do you inspectors > have any recommendations? GnuPG only uses libraries from the GnuPG suite (libgcrypt and friends). The discussion in this thread is about third party libraries producing broken PGP keys. OP hasn't answered which library was used to generate these keys. sam --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEBBAEWCgCpFiEEJaa7iN2bdkxrVUHCc4QJ9SDfkZAFAmoal+0bFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMiwyXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25z Lm9wZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQyNUE2QkI4OEREOUI3NjRDNkI1NTQx QzI3Mzg0MDlGNTIwREY5MTkwDxxzYW1AZ2VudG9vLm9yZwAKCRBzhAn1IN+RkIGQ AP9JUZMxmTzjBYslkHbDnYAi2VTU2QyWUuXl3ZnCqm2MxwD/Ran5T8XklUUDXX4D BBNi1tbcRVxtJmWUJeREXQRjBwU= =04qN -----END PGP SIGNATURE----- --=-=-=-- --===============4050969435964027806== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Gnupg-users mailing list [email protected] https://lists.gnupg.org/mailman/listinfo/gnupg-users --===============4050969435964027806==--