Are you worried about people discovering this relationship, or confirming a
suspected relationship?
Confirming it, possibly many years after it has been dissolved.
Future is the key-word here.
In that context, then-current response of a key-server query on
"" could be much more deleterious to
This sounds like a perfect use case for WKD
You are correct.
But the reason for my original post was not to find
better ways of communication mechanics while the
relationship exists, it was specific and quite narrow:
how can both sides do all they reasonably can in order
to avoid making it
> On 31 Jan 2022, at 21:39, jonkomer wrote:
>
> There is significant difference between a one-time
> "third-party" correspondent misusing his knowledge of
> the relationship after it has been dissolved, from
> that same knowledge being published in perpetuity via
> a simple, automated Internet
On Mon, 31 Jan 2022 01:09, Ángel said:
> Nothing in the email you receive is actually required. You could have a
> Fully-Encrypted-Email-Messages, which on SMTP looked like:
>
> MAIL FROM:<...>
> RCPT TO:
> DATA
>
>
> .
> QUIT
>
>
> No plaintext at all. (Well, some Received: headers would be
I go away for the weekend, and my mailbox catches fire... ;-)
On 29/01/2022 16:38, jonkomer via Gnupg-users wrote:
> (a) Unfortunately, OpenPG email encryption is incompatible
> with GDPR and should not be used by those that either want
> or need to be GDPR compliant.
This is not so; the use of
On Montag, 31. Januar 2022 15:58:22 CET Piotr Morgwai Kotarbinski via Gnupg-
users wrote:
> I have a public key with a photo-ID uploaded to WKD at my domain and when I
download it manually and import to gpg, everything works as expected:
[...]
> However if I try to locate the same key
On 28/01/2022 20:02, jonkomer via Gnupg-users wrote:
>> A. G. via :
>> The short answer is "no", or at best "not yet"...
>
> Thank you very much for the response and comprehensive
> comments.
>
> In this case, the mail domain owner is actually the one
> that needs this level of control: he
On 29/01/2022 01:55, Johan Wevers via Gnupg-users wrote:
> There are known technical issues: the HKP keyserver does not allow keys
> to be removed, GDPR or not. When the keyserer operator operates outside
> of the EU I don't think that is a legal problem.
This is incorrect. All three of the
On 29/01/2022 03:51, Shawn K. Quinn via Gnupg-users wrote:
> If the server is physically in the US, administered by someone residing
> in the US, is the EU really expecting US courts to enforce EU
> laws/directives like the GDPR on a US citizen?
The short answer is no, of course not.
The
On 30/01/2022 10:12, Klaus Ethgen wrote:
>
> When it comes to keyservers, with the same argument you could state that
> bitcoin is illegal. (No information in the key chain can be removed. And
> there is even child porn inside that key chain that could never ever
> again be removed!)
>
> There
Werner Koch via Gnupg-users writes:
> scdaemon does not see any reader. That might simply due to another
> process which uses the reader (the yubikey tools).
None the wiser:
$ cat ~/.gnupg/scdaemon.conf
debug cardio
verbose
log-file /tmp/scd.log
pcsc-shared
$ gpgconf
Hello all,
I have a public key with a photo-ID uploaded to WKD at my domain and when I
download it manually and import to gpg, everything works as expected:
> ubuntu@sandbox-jammy:~$ mkdir curl
> ubuntu@sandbox-jammy:~$ chmod 0700 curl
> ubuntu@sandbox-jammy:~$ gpg --homedir curl --list-keys
>
12 matches
Mail list logo
