> I believe that the key I'm signing this message with is 2048 bits and
> will expire next year. If I've got either of those details wrong, please
> correct my error(s).
No. There's no expiration date on your certificate, and it's a 4096-bit
RSA keypair.
> What size key do you recommend I
Please forgive me for piling several questions into a single post. If
anyone wants to just answer a subset, I'll still be very happy to read
your advice.
I believe that the key I'm signing this message with is 2048 bits and
will expire next year. If I've got either of those details wrong, please
On 09/11/17 00:39, listo factor via Gnupg-users wrote:
> Real-life threat-models are much more varied than what Alice, Bob
> and Eve would have us believe.
Hey, note that I'm not advocating against this proposed new alternative;
it sounds like you think I do. I explicitly said I'm not commenting
On Tue, 7 Nov 2017 14:45, gnupg-users@gnupg.org said:
> Could you elaborate on the 'why' part of this enforced pinentry usage
> with GnuPG? It wasn't mandatory in 1.x, now it's forced on us.
It is definitely not new. GnuPG 1.9 was released 14 years ago (it was
renamed to 2.0 2.0 11 years ago).
On Wed, 8 Nov 2017 12:28, r...@splintermail.com said:
> Yes, I reset my gpg-agent (killall -1 gpg-agent) each time, and was
> prompted with a pinentry prompt each time.
[ Please use "pkill -HUP gpg-agent" and never ever killall - which has,
aehm, funny effects on other Unices. ]
gpgconf
