Home → Beta →

gpg2 --refresh-keys broke

• Edit

alwillis

26 Mar, 2015 09:10 AM

I spend a lot of time in the terminal; before beta6, I could do gpg2 --refresh-keys at the command line, which just worked.

Now I get an error message for every key, similar to this: gpg: DBG: armor-keys-failed (KEY 0xFD3251B94C0D16A94DB799DE69C5D89B1D65079E BEGIN ) ->0.

I’m running 10.10.3 build 14D113c, the latest public beta of 10.10.3.

1. Support Staff 1 Posted by Luke Le on 26 Mar, 2015 02:47 PM

   

   Hi,

   we're seeing a similar output here and there are some reports to be found on google from linux users as well. Apparently it's not a problem, but it's best to ask on the gnupg mailing list (https://www.gnupg.org/documentation/mailing-lists.html). You should be able to get a answer there quickly.

   • Edit

2. 2 Posted by Martin on 27 Mar, 2015 09:01 PM

   

   To avoid repeated questions to the gnupg mailing list, can you post the answer you receive to this thread? I'm experiencing the same issue.

   • Edit

3. 3 Posted by Ben on 05 Apr, 2015 12:14 PM

   

   This is a very minor bug which was introduced in the most recent release(s) of at least GPG 1.4.19 and 2.0.27 (I haven't seen it with 2.1.2). It doesn't mean anything of importance, it's just a relic of the pre-release debugging process which Werner forgot to remove before the release. It won't be there in the next one.

   If you want to fix it before the next release you will need to patch the source code and recompile using the patch Werner sent to the list, which is this one:

   --8<---------------cut here---------------start------------->8--- commit 936416690e6c889505d84fe96983a66983beae5e
   Author: Werner Koch [email blocked]
   Date: Thu Feb 26 09:38:58 2015 +0100

   gpg: Remove left-over debug message.
   
   * g10/armor.c (check_input): Remove log_debug.
   
   Modified   g10/armor.c
   

   diff --git a/g10/armor.c b/g10/armor.c
   index 6c0013d..de1726d 100644
   --- a/g10/armor.c +++ b/g10/armor.c @@ -534,9 +534,6 @@ check_input( armor_filter_context_t afx, IOBUF a ) / This is probably input from a keyserver helper and we have not yet seen an error line. */ afx->key_failed_code = parse_key_failed_line (line+4, len-4); - log_debug ("armor-keys-failed (%.*s) ->%d\n", - (int)len, line, - afx->key_failed_code); } if( i >= 0 && !(afx->only_keyblocks && i != 1 && i != 5 && i != 6 )) { hdr_line = i; --8<---------------cut here---------------end--------------->8---

   • Edit

4. Support Staff 4 Posted by Steve on 07 Apr, 2015 01:12 PM

   

   Ben, thanks a lot for posting the mailing list reply here.

   • Edit

5. Steve closed this discussion on 14 Aug, 2015 12:57 PM.