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
Il 16/06/2018 19:48, Jeff Martin ha scritto:
> I'm not on Linux. I'm on macOS, which does not come with any built-in
> GPG. I must build GPG from source files. The only way to verify the
> source files in this situation (I think) is by checksum.
You can just fire up a VM booting with an "old
NdK wrote:
> GPG is usually included
I'm not on Linux. I'm on macOS, which does not come with any built-in
GPG. I must build GPG from source files. The only way to verify the
source files in this situation (I think) is by checksum.
On Mon, Jun 11, 2018 at 2:38 AM, NdK wrote:
> Il 09/06/2018
Lee wrote:
> So you still need to find a release announcement on 2 or 3 different
> sites to check the signing key fingerprints.
You have hit the heart of my problem. I cannot find these 2 or 3 different sites
That is why I came to this mailing list: for hints on how to find
these other sites.
My
