Re: Prefer a currently available signing subkey?

On 2017-04-19 at 17:46, Daniel Kahn Gillmor wrote: > The open report is https://dev.gnupg.org/T1983 Is it possible that is a duplicate of this report too? https://dev.gnupg.org/T1967 Both are about a capable subkey not being used on GnuPG Modern branch because it prefers a subkey with its missing

Re: Prefer a currently available signing subkey?

On 4/20/17 5:00 AM, Andrew Stubbs via Gnupg-users wrote: > even if the encryption key is the same. Oh, this brings up a related issue, actually! GnuPG doesn't cope very well if you put the same subkey on *multiple* smartcards - it remembers the first smartcard it saw that contained the subkey and a

Bad passphrase with gpg 2.1 - works fine with gpg 1.4

Hi all, After upgrading to Ubuntu 17.04, gpg does not accept my passphrase. More precisely, gpg 2.1.15 does not. However, gpg 1.4.21, installed as gpg1 does accept that very same passphrase. What am I doing wrong? Before upgrading, on Ubuntu 16.04, I'm fairly certain that I used gpg 1.4.x, and th

Re: Prefer a currently available signing subkey?

Yes, this affects me too - sorry for the "me too" email! It has actually prevented me from registering my key on keybase.io (if that's a "thing") --- I suppose I could go through the rigmarole of building the Faraday cage, getting the offline key out and revoking the offending signing keys, as if

Re: Cannot encrypt to reenabled key after migration

Hi MFPA-- On Wed 2017-04-12 15:21:38 +0100, MFPA wrote: > I have encountered a problem with 2.1.20 writing to my public keyring. > I was using the pre-compiled binaries on Windows 10. > > When editing/refreshing keys, or running gpg --check-trustdb, at the > end of the operation the command window

Re: Prefer a currently available signing subkey?

On Tue 2017-04-18 15:41:08 +, Arthur Ulfeldt wrote: > I had exactly the same problem, and there is an open bug about this (wanna > fix it?) I forgot the number. The open report is https://dev.gnupg.org/T1983 I've just moved this to priority "high" since it seems to continue to affect people.

Error decrypting after upgrading gpg (Windows)

Hi, After upgrading from 1.2.2. to 2.0.30 we have problems decrypting files from our partner C:\Temp\GnuPGtemp>gpg --version gpg (GnuPG) 2.0.30 (Gpg4win 2.3.3) libgcrypt 1.6.6 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later