On 17-08-2014 12:15, Armin K. wrote: > On 17.08.2014 16:57, Armin K. wrote: >> On 17.8.2014 16:56, Fernando de Oliveira wrote: >>> On 17-08-2014 09:47, Armin K. wrote: >>>> On 08/17/2014 01:39 AM, [email protected] wrote: >>>>> Author: fernando >>>>> Date: Sat Aug 16 16:39:09 2014 >>>>> New Revision: 13927 >>>>> >>>>> Log: >>>> >>>> ... >>>> >>>>> MIT Kerberos V5-1.12.2: update gpg2 >>>> >>>> Does the verification work for you? The key used to sign the latest >>>> release is different and I can't seem to receieve it from a hkp server.
>>> Solved problem: >>> >>> $ env LC_ALL=C gpg2 --recv-keys --pgp2 749D7889 >>> gpg: requesting key 749D7889 from hkp server keys.gnupg.net >>> gpg: key 749D7889: public key "Tom Yu <[email protected]>" imported >>> gpg: no ultimately trusted keys found >>> gpg: Total number processed: 1 >>> >>> Now, verification works. >>> >>> Notice the option --pgp2. >>> >>> It would be better to include a comment about this switch, instead of >>> including it in the command. What do you think? >>> >> >> I'll check it later, but I think it would be a nice idea to include it >> by default. > > Works perfectly now. Thanks for the quick solution. Fixed at revision 13937. Thanks. I am not happy with one thing that I introduced, to be more like what gpg2 outputs, older text was too different: "You will probably see output similar to: gpg: Signature made Mon Aug 11 22:53:10 2014 GMT using RSA key ID 749D7889 gpg: Good signature from "Tom Yu <[email protected]>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner." It is too frightening and also displays a name and email in a web page. Would appreciate any suggestions, please. -- []s, Fernando -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
