[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sks-devel] Implications of GDPR
From: |
Andrew Gallagher |
Subject: |
Re: [Sks-devel] Implications of GDPR |
Date: |
Thu, 3 May 2018 13:58:50 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 |
On 03/05/18 12:40, Moritz Wirth wrote:
> What about only accepting valid keys and removing all revoked or expired
> keys from the database?
I assume you mean "remove the user-id packets of all revoked or expired
keys"? You would have to retain at least the revocation signature and
the primary key, to make sure that nobody tried to re-upload a
non-revoked copy of the key, and to make sure that the keyservers still
served their primary purpose of distributing key revocations.
But the primary key could itself be considered personal data...
--
Andrew Gallagher
signature.asc
Description: OpenPGP digital signature
- Re: [Sks-devel] Implications of GDPR, Mike O'Connor, 2018/05/03
- Re: [Sks-devel] Implications of GDPR, Gabor Kiss, 2018/05/03
- Re: [Sks-devel] Implications of GDPR, Ari Trachtenberg, 2018/05/03
- Re: [Sks-devel] Implications of GDPR, brent s., 2018/05/03
- Re: [Sks-devel] Implications of GDPR, Daniel Roesler, 2018/05/03
- Re: [Sks-devel] Implications of GDPR, dirk astrath, 2018/05/04
- Re: [Sks-devel] Implications of GDPR, Arnold, 2018/05/04
- Re: [Sks-devel] Implications of GDPR, Andrew Gallagher, 2018/05/04