On Mon, 3 Oct 2022, Phil Pennock via Gnupg-users wrote:
Folks,
I setup WKD for work a while back, to publish the PGP keys for those who
had them. Then in November I removed the first key because it was
causing Protonmail users to keep sending encrypted to the recipient and
a lot of his
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 4 Aug 2022, Jan Eden via Gnupg-users wrote:
Hi,
I just check for a list of ransomware filename patterns (e.g.
*.cryptotorlocker*).
Best regards,
Jan
On 2022-08-04 18:58, Uwe Brauer via Gnupg-users wrote:
Hi
I apologize for this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 26 Oct 2021, Robert J. Hansen via Gnupg-users wrote:
all is well and good. At least, on Windows. But what about linux?
As a general rule, Windows signs executables more than it signs packages;
Linux signs packages more than it signs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 22 Oct 2021, Bernhard Reiter wrote:
Hello friends of OpenPGP,
Hi!
as part of his Bachelor thesis [1], Christoph wants so to find out, which
actions could increase the overall usage of WKD.
There are two parts of the usage: The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
have a look at the manpage at --export-secret-keys:
"Same as --export, but exports the secret keys instead. ..."
regards,
Erich
On Thu, 20 May 2021, sergio via Gnupg-users wrote:
I have generated a key on host A and it works fine:
A $
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On Wed, 24 Feb 2021, Werner Koch wrote:
On Fri, 22 Jan 2021 20:59, Erich Eckner said:
Thank you for your time! For everyone to benefit from my problem, I'd like
to suggest to clarify in the documentation, that and how tor will be
I'll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I wanted to ask for help regarding this wkd-key-installation issue I had,
once more.
Whichever way I try, I always end up with an expired key being installed
into wkd, although the key file looks all-right to me:
$ gpg --show-keys
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 12 Feb 2021, Werner Koch wrote:
On Fri, 12 Feb 2021 11:44, Erich Eckner said:
$GPG --export --export-filter keep-uid="mbox = $mbox" $fpr
gpg-wks-client does something similar but using "uid =" with a
pre-checked UID in an import
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I'm using the following command to export keys for wkd:
$GPG --export --export-filter keep-uid="mbox = $mbox" $fpr
However, this creates funny results for the key for
buildmas...@archlinux32.org which is downloadable here:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 22 Jan 2021, Erich Eckner via Gnupg-users wrote:
I was more wondering, why gpg decides to go into "tor mode" on box #2, when
there is actually no tor installed or running. I'm totally happy to force
non-tor mode via config fil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
first: Maybe I should migrate this discussion to the bug tracker? But I'm
always somewhat hesitant to open new bugs, because I always assume, I'm
just too stupid to properly configure everything :-)
On Fri, 22 Jan 2021, Werner Koch wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 22 Jan 2021, Werner Koch wrote:
On Thu, 21 Jan 2021 15:05, Erich Eckner said:
2021-01-21 14:41:32 dirmngr[3623955.6] DBG: dns: libdns initialized (tor mode)
2021-01-21 14:41:32 dirmngr[3623955.6] DBG: dns:
Your are using Tor for DNS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 20 Jan 2021, Werner Koch wrote:
On Wed, 20 Jan 2021 14:46, Erich Eckner said:
is queried. This resolves to some old address (my DNS configuration
error), which serves the wrong content. Is it right, that this SRV record
should be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 20 Jan 2021, Werner Koch wrote:
On Tue, 19 Jan 2021 17:24, Erich Eckner said:
error in the subject when doing `gpg - --locate-external-keys
Many -v don't really help here because the actual task is done by the
dirmngr process.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 19 Jan 2021, Stefan Claas wrote:
On Tue, Jan 19, 2021 at 6:28 PM Stefan Claas
wrote:
On Tue, Jan 19, 2021 at 6:26 PM Erich Eckner via Gnupg-users
wrote:
Advanced method is set up, direct method is not. The key has multiple UIDs
(one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Stefan,
thanks for your answer.
On Tue, 19 Jan 2021, Stefan Claas wrote:
On Tue, Jan 19, 2021 at 5:24 PM Erich Eckner via Gnupg-users
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I'm playing around with my WKD setup (guess
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I'm playing around with my WKD setup (guess, why) and encountered the
error in the subject when doing `gpg - --locate-external-keys
er...@eckner.net`. Retrieving via curl and the manually-constructed url
works fine, also I cannot find
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 17 Jan 2021, Ingo Klöcker wrote:
On Sonntag, 17. Januar 2021 10:48:17 CET Erich Eckner via Gnupg-users wrote:
Hi all,
On Thu, 14 Jan 2021, Werner Koch via Gnupg-users wrote:
On Thu, 14 Jan 2021 01:47, Ángel said:
I understand
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 17 Jan 2021, Stefan Claas wrote:
On Sun, Jan 17, 2021 at 10:51 AM Erich Eckner via Gnupg-users
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
On Thu, 14 Jan 2021, Werner Koch via Gnupg-users wrote:
On Thu, 14 Jan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
On Thu, 14 Jan 2021, Werner Koch via Gnupg-users wrote:
On Thu, 14 Jan 2021 01:47, Ángel said:
I understand this to mean it as "only use the direct method if the
required sub-domain does not exist", with the SHOULD meaning that the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 13 Jan 2021, Juergen Bruckner via Gnupg-users wrote:
Hello Stefan!
Hi all,
[...]
sequoia did the right step and I hope for people relying on GnuPG that
it is possible for them in the future too.
So did Sequoia do that?
You
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 12 Dec 2020, Nicolas Boullis wrote:
Hi,
Hi Nicolas,
Since the smartcard that held all my subkeys died, I have to replace my
subkeys, and I’m willing to store them on several smartcards, just in
case I am unlucky again…
[ ... snip
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Matthias,
On Wed, 1 Apr 2020, Matthias Apitz wrote:
El día Mittwoch, April 01, 2020 a las 09:42:48 +0200, Ingo Klöcker escribió:
$ gpg --list-public-keys --with-colons g...@unixarea.de
tru::1:1585750650:0:3:1:5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 5 Sep 2019, john doe wrote:
On 9/4/2019 10:41 PM, Andre Klärner wrote:
Hi all,
is there a way to properly shared the entire keyring and trust settings
between two machines?
[ snip ]
The obvious solution would be to use mutt on your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi David,
here is, how I had thunderbird + enigmail running for several years with
two keys and without problems (I have switched away from thunderbird since
one year ago, because it got too heavy and slow for my taste):
For each sending
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 30 Jun 2019, Andrew Gallagher wrote:
On 2019/06/30 11:49, Mirimir via Gnupg-users wrote:
It would stop when certs can no longer be poisoned. And I don't see the
downside. I mean, what good does it do to have people downloading keys
that
26 matches
Mail list logo
