public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dane Smith <c1pher@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] validity of manifest signing key
Date: Fri, 25 Mar 2011 07:35:43 -0400	[thread overview]
Message-ID: <4D8C7E0F.5030702@gentoo.org> (raw)
In-Reply-To: <20110325094719.GB14321@denkmatte.mittag-leffler.se>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/25/2011 05:47 AM, Thomas Kahle wrote:
> Hi,
> 
> it says here http://www.gentoo.org/doc/en/gnupg-user.xml#doc_chap2 that
> the validity should be <6 month.  What is the protocol when the expiry
> date is approaching?
> 
> -) Extend expiry date and upload again?
> -) Create new key (and sign with ?? ) ?
> 
> Cheers,
> Thomas
> 

Traditionally you start using your new key the day your old key expires.

Having said that, <6 months seems a little paranoid, even by my
standards. (And I'm a professional paranoid) I'd say for a developer, ~
1 year is more than adequate.

- -- 
Dane Smith (c1pher)
Gentoo Linux Developer -- QA / Crypto / Sunrise / x86
RSA Key: http://pgp.mit.edu:11371/pks/lookup?search=0x0C2E1531&op=index
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJNjH4PAAoJEEsurZwMLhUxeKIQAIhZr9Q4cVQtD5Ru9tgral8z
bmdhFUrOEKo61H9/3KTgy8KowSNDm0UK+IoPEN/n8q/qMsu/0Ni0NHIJGZE6Lrbw
zxp4RpAQ8KQhWKXLppTVqedXLBChX5v6wGQJXlpd8xFg/drKTPo9U/r+W2F9Zs8n
bLmSzYnJqwd1NYBqBx4F4Vgdq2RO2iqugPMc8igNGvARjJirwcoJ32tqVq64rGke
NYrnjBaYV0EiexpS4crQRX3Ggf29CVgGlWnKKLLD5Nql3wmgT5P9DZASE0K2Pj5f
rmjjzNwq12YJN4UkJanbE+5c1Vd5FPk+k2RLMuLrQr8j8jUn/DzrY8NU3F5ioHV2
kvS/4W5uJ3h9xQYG5RzNek9ydYn3Be2T5+nXxZQJmaGZO56qeh1CRQSMRh6LI7Ys
/2KkIVsskJHt0IV+NSnc0KmleZbmWfXP1GkexZNDrswHTJ4HuTKuPYHxsIX8gvqO
zqPY+UxlQrj5esRUD1VBKbsi+J88zaT931sgHmeyLM55kBoA8zlZ6ZCI9PkzbfFg
fL74+qVn7hsVgFvI8C8PSCBpoCpxC6wNnJIG5Uz+NiZouEUB3i8W0HqqB1YI+67L
Pbbtc9/EREv1HQwDgM870ReYM1Fa/+qnl7TwcbhilkgzkSjXUjqinzuuwyGYw6ad
C3J0KAcCRr1XfjJQaY5k
=a5EG
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2011-03-25 11:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25  9:47 [gentoo-dev] validity of manifest signing key Thomas Kahle
2011-03-25  9:55 ` Antoni Grzymala
2011-03-25 10:18   ` Christoph Mende
2011-06-25  7:37   ` justin
2011-06-25  7:44     ` Michał Górny
2011-03-25 11:35 ` Dane Smith [this message]
2011-06-26 14:21   ` Marc Schiffbauer
2011-03-25 14:46 ` Michał Górny
2011-03-25 14:53   ` Andreas K. Huettel
2011-03-25 18:58     ` Mike Frysinger
2011-03-25 16:35 ` Robin H. Johnson
2011-03-25 20:08   ` Mike Frysinger
2011-03-25 19:00 ` Mike Frysinger
2011-03-25 19:42   ` Andreas K. Huettel
2011-03-26  9:36   ` "Paweł Hajdan, Jr."

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=4D8C7E0F.5030702@gentoo.org \
    --to=c1pher@gentoo.org \
    --cc=gentoo-dev@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