Hello or Salaam everyone,
I have a few questions regarding password hashing in general. And would very
much appreciate any advice (just try not to use harsh words, please ;) )
Before that, I want to tell you something brief about what I'm doing. Basically
I'm building a product that you can
On Fri, 23 Nov 2018 15:18, gnupg-users@gnupg.org said:
> gcry_version_check(1.8.4)
gcry_check_version requires a string with the version number or NULL.
Thus
--8<---cut here---start->8---
const char *s;
if ((s=gcry_version_check ("1.8.4")))
printf
Hi,
if you can compile a not too old gpg version, you might be able to apply
this patch. It should show you the fingerprint of the cuplrit.
--8<---cut here---start->8---
diff --git a/g10/keyid.c b/g10/keyid.c
index a9034ee46..3694c26cc 100644
---
On Fri, 23 Nov 2018 18:56, dirk.gottschalk1...@googlemail.com said:
> I saw the Listing in the debugging log. I tried this also.
> gpg -k does not show this message, but two messages regarding two keys,
Hmmm, not easy to debug by mail.
> gpg: bad data signature from key 2894CD20EE47166D: Wrong
Hello.
Am Freitag, den 23.11.2018, 16:41 +0100 schrieb Werner Koch:
> On Thu, 22 Nov 2018 16:38, gnupg-users@gnupg.org said:
> > After listing the keys, gpg reports: gpg: error computing keygrip
> Looks like you have a garbled key or one with an unknown encryption
> algorithm. Not easy to
Hi,
can anyone tell me the syntax of the gcry_cry_version function? Does it work in
this way:
gcry_version_check(1.8.4)
??
Sent from ProtonMail mobile___
Gnupg-users mailing list
Gnupg-users@gnupg.org
On Thu, 22 Nov 2018 16:38, gnupg-users@gnupg.org said:
> After listing the keys, gpg reports: gpg: error computing keygrip
Looks like you have a garbled key or one with an unknown encryption
algorithm. Not easy to pinpoint because that diagnostics comes from the
deep innards of gpg.
Do you see
