Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU |
It should be noted that if the key is expired, then most likely all previous signatures on it are almost certainly also expired. And I'm not sure if the key servers will accept an extension of the expiration date, at least after it's already expired.If I'm remembering correctly, I think I ran into this problem several years ago when I tried to extend the expiration date on one of my keys. On Tue, Oct 1, 2013 at 11:29 PM, Derek Martin <invalid at pizzashack.org>wrote: > On Wed, Sep 18, 2013 at 08:12:09AM -0400, Dan Ritter wrote: > > On Wed, Sep 18, 2013 at 08:02:18AM -0400, David Kramer wrote: > > > Sooo, I used to be all about the PGP thing, but then I let it lapse and > > > it's long expired. I assume there's no way to un-expire it. > > > > Correct. > > Not so. You can change the expiration of an expired key via the > "expire" command from the menu provided by gpg --edit-key. Though, > there's a reason we expire keys, so... > > Anyway: > > $ gpg --edit-key 5CDBD469 > Secret key is available. > > pub 2048R/5CDBD469 created: 2013-09-23 expired: 2013-09-24 usage: SC > trust: ultimate validity: expired > sub 2048R/0E99CC6A created: 2013-09-23 expired: 2013-09-24 usage: E > [ expired] (1). John Smith (test key) <johnsmith at example.com> > > gpg> expire > Changing expiration time for the primary key. > Please specify how long the key should be valid. > 0 = key does not expire > <n> = key expires in n days > <n>w = key expires in n weeks > <n>m = key expires in n months > <n>y = key expires in n years > Key is valid for? (0) 365 > Key expires at Wed 01 Oct 2014 11:21:40 PM EDT > Is this correct? (y/N) y > > pub 2048R/5CDBD469 created: 2013-09-23 expires: 2014-10-02 usage: SC > trust: ultimate validity: ultimate > sub 2048R/0E99CC6A created: 2013-09-23 expired: 2013-09-24 usage: E > [ultimate] (1). John Smith (test key) <johnsmith at example.com> > > gpg> key 1 > > pub 2048R/5CDBD469 created: 2013-09-23 expires: 2014-10-02 usage: SC > trust: ultimate validity: ultimate > sub* 2048R/0E99CC6A created: 2013-09-23 expired: 2013-09-24 usage: E > [ultimate] (1). John Smith (test key) <johnsmith at example.com> > > gpg> expire > Changing expiration time for a subkey. > Please specify how long the key should be valid. > 0 = key does not expire > <n> = key expires in n days > <n>w = key expires in n weeks > <n>m = key expires in n months > <n>y = key expires in n years > Key is valid for? (0) 365 > Key expires at Wed 01 Oct 2014 11:26:59 PM EDT > Is this correct? (y/N) y > > pub 2048R/5CDBD469 created: 2013-09-23 expires: 2014-10-02 usage: SC > trust: ultimate validity: ultimate > sub* 2048R/0E99CC6A created: 2013-09-23 expires: 2014-10-02 usage: E > [ultimate] (1). John Smith (test key) <johnsmith at example.com> > > gpg> save > > > > Should I create a new one? > > > > Yes. > > Very probably. > > -- > Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 > -=-=-=-=- > This message is posted from an invalid address. Replying to it will > result in > undeliverable mail due to spam prevention. Sorry for the inconvenience. > > > _______________________________________________ > Discuss mailing list > Discuss at blu.org > http://lists.blu.org/mailman/listinfo/discuss > > -- John Abreau / Executive Director, Boston Linux & Unix Email jabr at blu.org / WWW http://www.abreau.net / 2013 PGP-Key-ID 0x920063C6 2013 / ID 0x920063C6 / FP A5AD 6BE1 FEFE 8E4F 5C23 C2D0 E885 E17C 9200 63C6 2011 / ID 0x32A492D8 / FP 7834 AEC2 EFA3 565C A4B6 9BA4 0ACB AD85 32A4 92D8
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |