unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Craven <david@craven.ch>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Key 69096DFDD7028BEDACC5884BC5E051C79C0BECDB "Key has been compromised"
Date: Tue, 28 Feb 2017 11:04:12 +0100	[thread overview]
Message-ID: <CAL1_im=U8=bh73_GJapPctEC+s9CFh1Q4YOvgY83n1EUk4CZqw@mail.gmail.com> (raw)
In-Reply-To: <20170227234148.GA13106@jasmine>

Hi Leo

> Can you clarify whether the key was deleted inadvertently, or if you
> think it was actually "compromised". To me, key compromise means you
> believe that the private key could have been copied by a 3rd party.

Key revocation certificates are generated before something happens.

It is possible, but unlikely that someone obtained my key file. There is
a strong password on it however, and I'm not aware of anyone using my
key. The signature should be valid for all before the revocation date and
for none after.

David

      reply	other threads:[~2017-02-28 10:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27 23:25 Key 69096DFDD7028BEDACC5884BC5E051C79C0BECDB "Key has been compromised" Leo Famulari
2017-02-27 23:41 ` Leo Famulari
2017-02-28 10:04   ` David Craven [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAL1_im=U8=bh73_GJapPctEC+s9CFh1Q4YOvgY83n1EUk4CZqw@mail.gmail.com' \
    --to=david@craven.ch \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).