invalid gpg key revocation
auto15963931 at hushmail.com
auto15963931 at hushmail.com
Mon Mar 5 18:12:24 CET 2012
I am 99.9% sure no one has gotten access to my machine or my keys.
If they had, I have to believe that there would have been more
damage done than this, and that does not appear to have happened. I
mention the details, which may seem irrelevant, only because
sometimes the devil is in the details. This event has in fact
occurred, and I need to figure out how to explain it and prevent
it. There was no revocation certificate for the key in question.
There has to be another explanation. If this was user error, then I
want to find that as well. What can be looked at on the revoked key
to see how or under what circumstances it was revoked? Thanks.
On Sun, 04 Mar 2012 22:29:30 +0000 Hauke Laging
<mailinglisten at hauke-laging.de> wrote:
>Am Sonntag, 4. März 2012, 22:13:58 schrieb
>auto15963931 at hushmail.com:
>
>> how is it then possible that someone
>> else would be able to get the key revoked even while I had not
>> published it to a key server at all? I mean, suppose someone
>wanted
>> to "mess around" with me and have my key revoked. How could
>that
>> have been done? Can it be prevented? Thank you.
>
>The interesting question about that is not about you publishing
>the public key
>but about how the person could get access to your private key. It
>is not
>possible to revoke a key without the private key. That answers
>your question
>how to prevent that: Pay attention to it that nobody gets access
>to your
>private keys.
>
>
>Hauke
>--
>PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814
More information about the Gnupg-users
mailing list