----- Original Message ----- | From: "Thorsten Glaser" <[email protected]> | Cc: [email protected] | Sent: Sunday, December 20, 2015 8:59:20 PM | Subject: Re: [Lynx-dev] ANN: lynx2.8.9dev.7 | | Thomas Dickey dixit… | >On Mon, Dec 21, 2015 at 12:18:35AM +0100, Axel Beckert wrote: | | >> P.S.: You seem to have signed Lynx releases with the GPG key | >> 5DDF8FB7688E31A6 in the past, but this release is signed with | >> 702353E0F7E48EDB. While 5DDF8FB7688E31A6 has a signature from | >> 702353E0F7E48EDB, 702353E0F7E48EDB hasn't been signed (publically | >> known) by 5DDF8FB7688E31A6. It would be nice if the current key | >> used | >> to sign releases is also signed by the key previously used for | >> that. | > | >I'll see how to do this (I haven't lost any keys, but hadn't thought | >to connect these). | | >One awkward problem with changing 5DDF8FB7688E31A6 is that its | >associated email address has been defunct for quite a while. | | PGP doesn’t care about eMail addresses – uids are mostly opaque. | | $ gpg -u 5DDF8FB7688E31A6 --edit-key 702353E0F7E48EDB | gpg> tsign | […] | gpg> save | $ gpg --keyserver hkp://pgp.surfnet.nl --send-keys 702353E0F7E48EDB
yes... but the registry which periodically asks for verification seems to care :-) -- Thomas E. Dickey <[email protected]> http://invisible-island.net ftp://invisible-island.net _______________________________________________ Lynx-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lynx-dev
