Difficulty of fixing reconciliation

Peter Lebbing peter at digitalbrains.com
Wed Aug 14 13:06:55 CEST 2019

On 14/08/2019 12:09, Andrew Gallagher wrote:
> Indeed, but that condition is fundamentally incompatible with
> decentralised reconciliation - because deletion without permissions
> management is an open door, and permissions have to be enforced by an
> authority.

Hmmmm.... the authority could just be the primary key that the
third-party signatures are over. I'm not talking about the current SKS
keyserver network, but some still-to-be-created federated synchronizing

That authority could also authorize no longer sharing a particular third
party signature, I think. It might still circulate in the federated
network, but any time it rears its head again it could get ignored by
the revoked authorization (or more: authorization to revoke). "Ignoring"
might just mean not offering it to clients even though it's still part
of the federation for technical purposes.

There's a lot of chance for misunderstandings here. I started writing
something less ambiguous and stopped due to the amount of work :-).



I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at <http://digitalbrains.com/2012/openpgp-key-peter>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20190814/2523ff22/attachment.sig>

More information about the Gnupg-users mailing list