On Sun, 25 Apr 2021 16:41, William Holmes said:
> I encrypted the file with '--hidden-recipient'.
> After decryption failed, gpg-agent was killed.
Right, I was able to valgrind the bug. We will have a solution soon.
> pub ed25519/0xFB3157F958F70A96 2021-04-25 [SC]
Better don't use the keyids
On Mon, Apr 26, 2021 at 12:05 PM Werner Koch wrote:
> You may want to open a bug report at dev.gnupg.org so that we don't
> forget about this.
Thanks for the tip, I’ll be sure to do so next time!
However in this case I have already submitted a patch to gnupg-devel yesterday.
I hope you don’t fo
On Sun, 25 Apr 2021 23:12, Shawn K. Quinn said:
> Now, for me, that begs the question: what does the internal random pool
> offer that simply using /dev/random (or better yet a quality HWRNG) does
> not?
It speeds up the initial seeding of gpg and gpg-agent's the internal
RNGs if the system's ent
On Sun, 25 Apr 2021 22:07, Kirill Elagin said:
> into `$HOME/.gnupg/scdaemon.conf`. I did not really try any other
> options, my understanding is that `debug-ccid-driver` (twice!) is what
Nope, that is todebug the low-level ccid driver. The best way to debug
the APDUs is
verbose
debug ipc,cardi
Hello all,
Thank you for your answers. Hope I respond to your questions:
I encrypt in my Shell as follows - I am doing it just now with a Backup File on
my desktop:
$ gpg bu_pw_new.txt.gpg
gpg: WARNING: no command supplied. Trying to guess what you mean ...
gpg: encrypted with 2048-bit ELG k
Hello Marek,
On Sun, 25 Apr 2021 17:31:53 +0200, Marek Stepanek
wrote:
> I am unsure how GnuPG could pick up the wrong key, which does not exist in my
> key deposit. My guess is, that it is encrypted anyway with my private key
Beware of a possible misunderstanding here: encryption is done with
