Date: Mon, 29 Sep 2014 04:45:21 +0200 From: beeessdee@ruggedinbox.com To: "Glen Barber" <gjb@FreeBSD.org> Cc: FreeBSD Release Engineering Team <re@freebsd.org>, freebsd-stable@freebsd.org Subject: Re: FreeBSD 10.1-BETA3 Now Available Message-ID: <fe17030e3efeefb5dfa800b46ee181d9.squirrel@s4bysmmsnraf7eut.onion> In-Reply-To: <20140928155118.GA75063@hub.FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
On Sun, 28 Sep 2014 11:51:18 -0400, "Glen Barber" <gjb@FreeBSD.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 Why 10.1-BETA3 announcement signed with not usual PGP key? gpgv: Signature made Sun Sep 28 11:51:18 2014 EDT using RSA key ID 478FE293 gpgv: Can't check signature: No public key Compare 10.1-BETA2 announce: gpgv: Signature made Sun Sep 21 13:06:56 2014 EDT using RSA key ID AF8B5ED0 gpgv: using subkey AF8B5ED0 instead of primary key A0B946A3 gpgv: Good signature from "Glen Barber <gjb@FreeBSD.org>" gpgv: aka "Glen Barber <glen.j.barber@gmail.com>" gpgv: aka "Glen Barber <gjb@glenbarber.us>" gpgv: textmode signature, digest algorithm SHA256 This key new last year/expire 2018, so very unexpected. Shocking it is: some people actually check this, not like http://xkcd.com/1181/ , you know. ;-) Seriously, SHA256 checksum on ftp mirror not so useful. PGP signed mail with checksum, who could guess, we actually use this and its not wasted efforts! Thanks.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fe17030e3efeefb5dfa800b46ee181d9.squirrel>
