Date: Thu, 09 Sep 2010 16:01:44 -0700 From: dougb@freebsd.org To: =?ISO-8859-1?Q?Tilman_Keskin=F6z?= <arved@FreeBSD.org> Cc: freebsd-doc@FreeBSD.org Subject: Re: expired PGP keys in handbook Message-ID: <4C896758.90505@freebsd.org> In-Reply-To: <4C87D051.1090806@FreeBSD.org> References: <4C87D051.1090806@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/8/2010 11:05 AM, Tilman Keskinöz wrote: > Hello doc people > > While updating my expired PGP key, i noticed i am not the only one: > > grep "expires: 200" doc/share/pgpkeys/* | grep -v sub | wc -l > 11 > > Maybe those committers that are still active should be poked to update > their keys. The best way to approach this is to poke people on an individual basis. I do this from time to time, but try not to do it so often as to be *overwhelmingly* annoying. :) Perhaps if I was not the only one doing it people would begin to see that this is an important area to keep up to date. OTOH, there is sometimes a valid reason to keep an expired key in the project keyring if that key has signed things in the past that we want to be able to easily verify signatures for in the future. OTOOH, there is hardly ever a good reason to set an expiration date for a key, and most people would be better served simply removing the expiry and pushing out the updated key. :) Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C896758.90505>