I tried the suggested commands below and had the same results.
The key generations never finishes
[cid:image002.jpg@01D638BC.16B954A0]
-Original Message-
From: Werner Koch
Sent: Tuesday, June 2, 2020 5:33 AM
To: Williams, Chad L via Gnupg-users
Cc: Williams, Chad L
Subject: Re
Hello Patrick,
> Let's first define Standard users. The majority of users who use
> smartcards that *I* know are expert or power users. They can handle this.
>
> The "Standard users" I have in mind don't use GnuPG for anything else
> than encrypting mails, and they don't use smartcards either. Th
On Fri, 29 May 2020 15:39, LisToFacTor said:
> vaguely as "group policies". Other than that, the only substantial
> change is the replacement of pgp 2.6.3ia-multi06 with gpg 1.4.10
You should not propose the use of 1.4 for any other use than decrypting
old data. In particular not in a guide whic
On Sat, 30 May 2020 14:51, Williams, Chad L said:
> Attempting to generate a key on Solaris 10 server using the below command
>
> gpg --full-generate-key --pinentry-mode=loopback
Do not use loopback unless you know what you are doing. Adding
--verbose should give you some insight what goes wrong.
On Sun, 31 May 2020 12:35, Patrick Brunschwig said:
> Let's first define Standard users. The majority of users who use
> smartcards that *I* know are expert or power users. They can handle this.
I have a different experience here and we are actually promoting the use
of smartcards because they be
On Sun, 31 May 2020 11:10, David Flory said:
> How does one identify a v3 key?
By trying to import it with gpg; you should get a hint that v3 keys are
not anymore supported.
Salam-Shalom,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
signature.asc
Description: PG
On Fri, 29 May 2020 14:43, karel-v_g--- said:
> But it's a pity that Thunderbird developed its own solution because of
> licensing issues while we have a proven working solution with GnuPG...
For the records: There is no licensing issue; it is just a Mozilla
policy issue not to use or depend on s
On Fri, 29 May 2020 17:54, Steffen Nurpmeso said:
> Looking at the source it seems libgcrypt knows about the Linux
> getrandom systemcall. Yet it does not seem to know about glibc's
> getrandom library function.
Which was not available back then when I implemented support for
getrandom. Further