From owner-freebsd-doc@FreeBSD.ORG Fri Apr 5 00:32:41 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CEBF0DFC; Fri, 5 Apr 2013 00:32:41 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id A69CB722; Fri, 5 Apr 2013 00:32:41 +0000 (UTC) Received: from glenbarber.us (70.15.88.86.res-cmts.sewb.ptd.net [70.15.88.86]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id 980DC23F804; Thu, 4 Apr 2013 20:32:40 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.8.0 onyx.glenbarber.us 980DC23F804 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Thu, 4 Apr 2013 20:32:38 -0400 From: Glen Barber To: mexas@bristol.ac.uk Subject: Re: http://www.freebsd.org/doc/handbook/pgpkeys-developers.html outdated? Message-ID: <20130405003238.GB1534@glenbarber.us> References: <201304042147.r34Llwnm083524@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="pvezYHf7grwyp3Bc" Content-Disposition: inline In-Reply-To: <201304042147.r34Llwnm083524@mech-cluster241.men.bris.ac.uk> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Apr 2013 00:32:41 -0000 --pvezYHf7grwyp3Bc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 04, 2013 at 10:47:58PM +0100, Anton Shterenlikht wrote: > I was looking for a real name of a developer > and noticed that many keys have long expired. > Should this info be updated? Or maybe these > people have left? >=20 It depends. Some keys go expired until the developer gets pinged about it, and updates their key. In other cases, the developer becomes inactive. Glen --pvezYHf7grwyp3Bc Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJRXhumAAoJEFJPDDeguUajP1IH/33ok8jIZs3JLikMxvlqFvqX A+EET9Ocr40KOQ0NvoFaMJg6GiNLhIyBVEe+QvwdQX1p7OqpVKD9akOTt3HGs6jR fUOnoV2e0v9gukYjnYXwdP2btVJC3/u0dEIKQbDVwn4mxvNQx0zmRArj7U+tF5ct tW53JeBqyuE2Dpt6z78ahndTslT5xKM0usALpc+HPbNQowCZTfKcmX1jDnNbh0pb FCl3C+IYokdm9IkRrkMAwg+J9vCiA/yLAyOFmYSRu9XITiJyVdnzPiBq2uDsrp1v 7Xsc17B1TLeen/+0TwpUGhD1npplag2UoxUvMQhlnBcQPUwH0whU6hVEQIld3cY= =YJqI -----END PGP SIGNATURE----- --pvezYHf7grwyp3Bc--