Date: Fri, 28 May 2010 13:46:06 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Remko Lodder <remko@FreeBSD.org> Cc: doc-committers@FreeBSD.org, cvs-doc@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: doc/share/pgpkeys remko.key Message-ID: <4C002B8E.8050402@FreeBSD.org> In-Reply-To: <201005282039.o4SKdOps000931@repoman.freebsd.org> References: <201005282039.o4SKdOps000931@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/28/10 13:39, Remko Lodder wrote: > remko 2010-05-28 20:39:24 UTC > > FreeBSD doc repository > > Modified files: > share/pgpkeys remko.key > Log: > Add a new key, the previous one had never ever been signed and I seem to have > expired it. I will try my best to get this key signed by at least a few > people, and extend the key when it expires .. > > Revision Changes Path > 1.3 +32 -35 doc/share/pgpkeys/remko.key > > http://www.FreeBSD.org/cgi/cvsweb.cgi/doc/share/pgpkeys/remko.key.diff?&r1=1.2&r2=1.3&f=h You can update keys after they expire, then push them out to the key servers and people will get the update when they refresh their keyrings. OTOH, unless you have a clear purpose in mind for setting an expire time for the key you're better off not setting one. 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?4C002B8E.8050402>