Re: Cannot encrypt to reenabled key after migration

2017-04-20 Thread Martin S.
Title: Re: Cannot encrypt to reenabled key after migration Hi Am Mittwoch, 12. April 2017, 13:45:09 schreiben Sie: Hey folks, I have a keypair that was created with gpg 1.4.20 and currently is disabled. I installed gpg 2.1.20 and tried to enable this key, but get the following error

Re: Cannot encrypt to reenabled key after migration

2017-04-19 Thread Daniel Kahn Gillmor
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

Re: Cannot encrypt to reenabled key after migration

2017-04-13 Thread Derek Tye
2017-04-12 16:21 GMT+02:00 MFPA <2014-667rhzu3dc-lists-gro...@riseup.net>: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > > > On Wednesday 12 April 2017 at 12:45:09 PM, in > , > Derek Tye wrote:- > > > > gpg: waiting

Re: Cannot encrypt to reenabled key after migration

2017-04-12 Thread MFPA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wednesday 12 April 2017 at 12:45:09 PM, in , Derek Tye wrote:- > gpg: waiting for file '.../gnupgHome/pubring.gpg' to > become accessible ... I have encountered a

Cannot encrypt to reenabled key after migration

2017-04-12 Thread Derek Tye
Hey folks, I have a keypair that was created with gpg 1.4.20 and currently is disabled. I installed gpg 2.1.20 and tried to enable this key, but get the following error: \>gpg --edit-key testkey gpg (GnuPG) 2.1.20; Copyright (C) 2017 Free Software Foundation, Inc. This is free software: you are