public inbox for gentoo-security@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-security@lists.gentoo.org
Subject: Re: [gentoo-security] Regeneration of gpg keys after HeartBleed
Date: Tue, 15 Apr 2014 09:28:23 -0400	[thread overview]
Message-ID: <CAGfcS_n_54n1JgKXSB8et1XPXJfK4cFFTzdd93WdXQ4p6DogfQ@mail.gmail.com> (raw)
In-Reply-To: <534C5927.1000800@gentoo.org>

On Mon, Apr 14, 2014 at 5:54 PM, Alex Legler <a3li@gentoo.org> wrote:
> On 09.04.2014 18:39, Jo wrote:
>> Hi all, this is my first post in this list, so again Hi all!
>>
>> I'm a bit concerned about the signing keys of the portage tree releases,
>> I know that gpg is not the same as openssl but keeping in mind that SSH,
>> VPN, HTTPS keys might be compromised for two years, don't you think it's
>> a healthy measure to generate a new pair of keys?
>
> GPG private keys are kept and used nowhere near any server processes,
> not transferred via HTTPS or any VPNs, and SSH is not affected. I don't
> see an immediate need to rotate them.

Agree.  Also, in a few months whenever the new GPG policy GLEP is
implemented I suspect that many keys will be regenerated anyway.

Rich


      reply	other threads:[~2014-04-15 13:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09 16:39 [gentoo-security] Regeneration of gpg keys after HeartBleed Jo
2014-04-09 17:01 ` Luis Ressel
2014-04-09 19:21   ` Chris Frederick
2014-04-10 23:45     ` Matthias Niethammer
2014-04-14 21:54 ` Alex Legler
2014-04-15 13:28   ` Rich Freeman [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

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

  git send-email \
    --in-reply-to=CAGfcS_n_54n1JgKXSB8et1XPXJfK4cFFTzdd93WdXQ4p6DogfQ@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-security@lists.gentoo.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox