Its quite simple really, you sign a revocation of the key and create a new
one, just like you'd do if you ever suspected your private key had been
compromised.

-R

On Fri, Aug 16, 2019 at 3:29 PM Stefan Claas <s...@300baud.de> wrote:

> Hendrik Visage wrote:
>
> > SKS network contains *PUBLIC* keys. It’s purpose, is to PUBLICLY make
> your
> > communications, signed/etc. with the associated *private* key, by
> directed to
> > you and associated with you to proof that it was *you* that
> > signed/produced/etc. that piece of communication. That purpose would be
> to
> > know that the communication was not forged as you, and thus people can
> take
> > that piece of communications as being your words spoken and trusted as
> it was
> > not somebody else faked you. It is also a mechanism that you can receive
> > communications, meant only for your eyes (I meant *private* key :) )that
> > nobody else can decode (given they’ve not compromised your private key).
> >
> > The fact that the SKS network had been and probably will still be
> > abused/DoSed/etc. we can’t deny, but once people becomes silly, as I see
> this
> > whole GDPR discussions have been, I have but one set of advice: Either
> you
> > fix it, or you get out of the SKS server network… let those that run the
> SKS
> > servers have the pains/legal battles/etc. when they are attacked by the
> GDPR
> > enforcers, we’ll fight that battle, no need to make our lives worse off
> if
> > you can’t add positive value…
> >
> > Yours enjoying his pop-corn reading these debates
>
> O.k. let's forget for a moment the GDPR.
>
> Would you or any other SKS operator in 2019 agree that a person should
> have the right that his / her public key can be removed from the SKS
> network if he / she asks for?
>
> An example: You have children and you recommend as an privacy advocate
> and parent that your minors should use PGP.
>
> A nasty classmate signs your daughters pub key with bad things. Teenagers
> usually smarter than their parents may not handle such a situation well,
> like us old PGP farts.
>
> Please explain in 2019 to you friends, wishing to learn secure email
> communications, that they should use PGP, while everybody can sign
> their pub key with arbritary  (and illegal) data, thanks to SKS.
>
> They will for sure show you a stinking finger.
>
> A public key in 2019 does not mean that it can be used for nasty
> things, while a public key holder can not defend him  / her self!
>
> May I ask why you SKS operators did not implemented GnuPG's
> feature the --no-modifiy flag? It is not a brand new feature ...
>
> Regards
> Stefan
>
> --
> box: 4a64758de9e8ceded2c481ee526440687fe2f3a828e3a813f87753ad30847b56
> GPG: C93E252DFB3B4DB7EAEB846AD8D464B35E12AB77 (avail. on Hagrid, WKD)
>
> _______________________________________________
> Sks-devel mailing list
> Sks-devel@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/sks-devel
>
_______________________________________________
Sks-devel mailing list
Sks-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/sks-devel

Reply via email to