Well I'll be that crazy monkey's crazy uncle!
I started from scratch -- copied the 2.0.20 .gnupg dir to the 2.2.24 machine,
and imported the secret key as the very first operation:
$ gpg --import <182E8151.exported
gpg: starting migration from earlier GnuPG versions
gpg: porting
On Tue, 19 Jun 2018 22:31, fe...@crowfix.com said:
> I tried both these steps, and neither changed anything. Import said it
> imported, but I have a saved copy of .gnupg, and there was no difference after
Did it say that an secret key was imported? You check your secret keys
using
gpg -K
On Mon, Jun 18, 2018 at 08:36:38AM +0200, Werner Koch wrote:
> On Mon, 18 Jun 2018 07:44, skqu...@rushpost.com said:
>
> > The format secret keys are stored in changed between 2.0.x and 2.1.x. It
> > is possible that 2.2.x no longer has the code in it to migrate to the
>
> 2.2 still has the
On Mon, Jun 18, 2018 at 03:19:53PM +0200, Kristian Fiskerstrand wrote:
> On 06/18/2018 03:06 PM, fe...@crowfix.com wrote:
> > Says it imported the secret keys, but doesn't show them.
>
> Any chance they are expired? Try playing with --list-options, in
> particular the show-unusable-* variants
>
On 06/18/2018 03:06 PM, fe...@crowfix.com wrote:
> Says it imported the secret keys, but doesn't show them.
Any chance they are expired? Try playing with --list-options, in
particular the show-unusable-* variants
Are they listed with --list-keys ?
Try importing the public keyring separately, in
On Mon, Jun 18, 2018 at 08:36:38AM +0200, Werner Koch wrote:
> On Mon, 18 Jun 2018 07:44, skqu...@rushpost.com said:
>
> > The format secret keys are stored in changed between 2.0.x and 2.1.x. It
> > is possible that 2.2.x no longer has the code in it to migrate to the
>
> 2.2 still has the
On Mon, 18 Jun 2018 07:44, skqu...@rushpost.com said:
> The format secret keys are stored in changed between 2.0.x and 2.1.x. It
> is possible that 2.2.x no longer has the code in it to migrate to the
2.2 still has the migration code. However, once a migration is done it
will not be done again.
On 06/17/2018 05:20 PM, fe...@crowfix.com wrote:
> gpg: encrypted with 2048-bit ELG key, ID 18DCDD20A3362105, created
> -mm-dd
> "Felix Finch (Scarecrow Repairman) "
> gpg: decryption failed: No secret key
The format secret keys are stored in changed between 2.0.x and
Hi Felix,
> gpg -e dest -r fe...@crowfix.com
...
> gpg: encrypted with 2048-bit ELG key, ID 18DCDD20A3362105, created
> -mm-dd
> "Felix Finch (Scarecrow Repairman) "
> gpg: decryption failed: No secret key
The key for recipient fe...@crowfix.com that was used to
I have a seldom-used need to encrypt a few files, and the last time I did was
on a gentoo system running 2.0.20.
gpg -e dest -r fe...@crowfix.com
I have migrated the .gnupg dir to an Ubuntu 18.04 system running 2.2.24, and
the gpg command seems to have mutated. The gentoo 2.0.20 command
10 matches
Mail list logo
