Re: [SLUG] gnugpg, add public key

From: Doug Koobs (dkoobs@dkoobs.com)
Date: Mon Feb 17 2003 - 10:03:46 EST


I wasn't sure if I was doing this correctly, so when I created, I set it
to expire in 1 day... I just trued to use

gpg --edit-key d7469a12

and used the "expire" option to change the key to never expire, but when
I do --list-keys, I still get

pub 1024D/D7469A12 2003-02-17 Doug Koobs <dkoobs@dkoobs.com>
sub 1024g/4C369838 2003-02-17 [expires: 2003-02-18]

I assume this means my key will still expire today, but I'm not sure
what the second line is... Any ideas?

Doug

On Mon, 2003-02-17 at 08:52, Ian C. Blenke wrote:
> On Sun, Feb 16, 2003 at 10:54:35PM -0500, Doug Koobs wrote:
> > OK, I found that I can use the command:
> >
> > gpg --keyserver wwwkeys.pgp.net --recv-keys <keyID>
> >
> > to import keys. I imported Brian's key, but when I view Brian's digital sig, I get the message:
> >
> > BAD signature from "J. Brian Coyle..."
> >
> > Am I still missing something?
> >
> > Doug
>
> Well, somehow you've managed to generate a key that expires tomorrow
> (2003/02/18). That's a rather short-lived key.
>
> Both of Brian's keys expire next month as well
>
> I've signed both Brian and your keys, which you may update by
> re-downloading your keys from the key server:
>
> gpg --keyserver wwwkeys.us.pgp.net -recv-keys D7469A12
>
> Not that this really matters, as all of the keys I've signed will expire
> tomorrow and next month anyway.
>
> - Ian
>





This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 15:28:08 EDT