Re: What causes this bad signature

On 18/11/15 16:59, da...@gbenet.com wrote: > 0x5E5CCCB4A4BF43D7 has expired - that's the only thing "bad" about it. I could not reproduce this: > $ gpg2 -k 2C53B2ED > pub rsa2048/2C53B2ED 2015-08-21 [expired: 2015-08-28] > uid [ expired] Test Teststra Jr. > $ gpg2

Re: What causes this bad signature

On 16/11/15 15:01, Sebastian Wiesinger wrote: > Hello, > > my key is not bad, the signature by 0x5E5CCCB4A4BF43D7 is bad. The > question is why. > > Regards > > Sebastian > Hello Sebastian, I downloaded the key and all sub-keys. Neither GPA Kgpg or Kleopatra give any warnings about this

Re: best practices for creating keys

On 17/11/15 15:33, Andrew Gallagher wrote: >> https://alexcabal.com/creating-the-perfect-gpg-keypair/ > > This is a fairly good article - I've used it myself for reference in the > past. Also have a look at: I disagree, I'd recommend people not to read that article, let alone follow its advice.

Re: What causes this bad signature

On 18/11/15 13:53, da...@gbenet.com wrote: > I downloaded the key and all sub-keys. Neither GPA Kgpg or Kleopatra give > any warnings > about this key. You don't say what's bad about it - which is why your not > getting much help > here. Actually, I understand what he means, I just don't know