On 29 May 2019, at 09:07, Werner Koch wrote:
> Which would support my point to redesign the keyservers to
>
> - Inhibit searches by user id.
What is the reasoning behind this (as signing keys just are on the uploaded key
with a keyid — so we are talking about the key its own data) ?
And pair
On Mon, 27 May 2019 13:30, kristian.fiskerstr...@sumptuouscapital.com
said:
> requiring load-balanced setup with minimum of 3 nodes on modern hardware
> (e.g a node today requires a minimum of 8 GiB of RAM to be responsive
> during merge of certain keys). The propagation time between the servers
On Sun, 26 May 2019 22:39, gnupg-de...@spodhuis.org said:
> With the various problems of SKS today, I tentatively suggest that not
> defaulting to the HKPS pool and choosing a different target for the
> keys.gnupg.net CNAME might be beneficial.
FWIW, keys.gnupg.net is since gnupg 2.2.7 not a
On 27/05/2019 14:47, Jim Popovitch wrote:
> On Mon, 2019-05-27 at 14:28 +0100, Andrew Gallagher wrote:
>> On 27/05/2019 12:47, deloptes wrote:
>>> it is a matter of an agreement between the person and the authority
>>> hosting the information of the public key
>
>> This is the problem though:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-05-27 at 14:28 +0100, Andrew Gallagher wrote:
> On 27/05/2019 12:47, deloptes wrote:
> > it is a matter of an agreement between the person and the authority
> > hosting the information of the public key
>
> This is the problem though:
On 27/05/2019 12:47, deloptes wrote:
> it is a matter of an agreement between the person and the authority
> hosting the information of the public key
This is the problem though: there is no single identifiable authority
(data controller in GDPR jargon) with whom to make such an agreement.
Hi all,
sorry for stepping in as I am not working on this topic, but following the
GDPA story for longer time I never read that we could simply prompt and
agree with the terms of the authority hosting the information of the
public key. The date and signature and probably reference to a version of
On 5/27/19 4:39 AM, Phil Pennock wrote:
> hkps is limited because Kristian doesn't hand out certs to anyone who
> shows up with a new keyserver and asks; he tends to do so with people
> who've been around and part of the community, because of the fairly
> obvious problems with assuming TLS is
Tobias Mueller:
So far, I stand by last year's statement:
tl;dr: Keep calm and keep running keyservers.
Are you standing by your statement because you believe that processing
that data is lawful or because you don't fear the consequences of a
potentially unlawful processing of data?
I stand
Hi,
On Mon, 2019-05-13 at 19:35 +0200, ilf wrote:
> So far, I stand by last year's statement:
>
> > tl;dr: Keep calm and keep running keyservers.
>
Are you standing by your statement because you believe that processing
that data is lawful or because you don't fear the consequences of a
On 2019-05-26 at 10:43 +0200, Werner Koch wrote:
> On Sat, 25 May 2019 14:53, i...@zeromail.org said:
> You mean from the left over 5 servers in the default hkps pool:
>
> pgpkeys.eu 51.38.91.189AS16276 (UK)
> pgpkeys.uk 192.146.137.98 AS57672 (UK)
> pgpkeys.co.uk
On Sat, 25 May 2019 14:53, i...@zeromail.org said:
> ilf:
>> Now I would like to know: Did any keyserver admin(s) receive any
>> (serious) GDPR-related complaint? Or even an official complaint by a
>> data protection authority? Or even a penalty like a fine?
You mean from the left over 5 servers
Hi,
On 19-05-13 23:23:45, Tobias Frei wrote:
> https://lists.nongnu.org/archive/html/sks-devel/2019-02/msg00070.html
I'm not completely sure what you want to say by posting this link, but,
right, that is one example of such a request, answered by Kristian, no
fine involved, AFAIK.
There were
Hi ilf,
https://lists.nongnu.org/archive/html/sks-devel/2019-02/msg00070.html
Best regards
Tobias Frei
___
Sks-devel mailing list
Sks-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/sks-devel
Almost one year ago, there was a big debate about the GDPR and
keyservers.
Now I would like to know: Did any keyserver admin(s) receive any
(serious) GDPR-related complaint? Or even an official complaint by a
data protection authority? Or even a penalty like a fine?
I assume not, at least
On 22.05.18 21:44, Vincent Breitmoser wrote:
[...]
> My personal conclusion is that keyservers that support user id packets are,
> quite simply, incompatible with GDPR law. Has anyone else thought about this?
> It's fairly unlikely that there will be actual consequences since keyservers
> aren't
Hi Vincent,
Am Dienstag 22 Mai 2018 21:44:09 schrieb Vincent Breitmoser:
> My personal conclusion is that keyservers that support user id packets are,
> quite simply, incompatible with GDPR law. Has anyone else thought about
> this?
thinking about earlier data privacy laws (which were quite
On 05/23/2018 11:27 AM, ilf wrote:
> tl;dr: Keep calm and keep running keyservers.
>
> Vincent Breitmoser:
>> (cross-posting on all the cool pgp lists)
>
> (I wonder, if this really needs to be an all the four lists. I think
> sks-devel@ might be the most appropriate. Having said that, I'm only
Am 22. Mai 2018 21:44:09 MESZ schrieb Vincent Breitmoser :
>Now, since the PII that is uploaded is not used to fulfill contractual
>obligations
I'm not a lawyer, but i see this vice versa.
Users upload their keys for the purpose of their usage in the "web of trust"
and
Sigh, I just now noticed that I wasn't actually subscribed to sks-devel anymore,
I thought I was. I humbly apologize for the noise, and will go read the
relevant threads now :)
- V
___
Sks-devel mailing list
Sks-devel@nongnu.org
Hey there,
(cross-posting on all the cool pgp lists)
so Dominik and I have been thinking a bit about how GDPR might affect
OpenKeychain, and its interoperability with public keyservers. Turns out this
is a hard question - in the end we couldn't answer whether publishing a tool
that offers
21 matches
Mail list logo