On 10/26/17, Wilfred van Velzen pondered and said...   
       
    Wv> idea. I have some keys from the early 90's that I don't remember the   
    Wv> passwords of, that just take up space on the keyservers, but I can't do   
    Wv> anything with.   
      
   Same here :)   
      
    Wv> It seems a rather short period.   
      
   Agreed... 3 years (see my other reply) may be better   
      
    Wv> If you sign your new key with the old one, there is a web of thrust that   
    Wv> goes back to the signers of the old key. But I don't know how that works   
    Wv> with expired keys. There is probably less thrust when there are expired   
    Wv> keys involved.   
      
   Had not considered that, an expired key to my mind is just that so I can't   
   see why anyone would want to include it in a future key?   
      
    Wv> Whatever period you choose, at least generate revokation certificates   
    Wv> and keep them in a save place, so if you loose the passwords of your key   
    Wv> you can still revoke them...   
      
   I need to learn how to do this and am not sure how to as yet, I'm using a   
   windows tool paired with the gnupgp ... hmmm   
      
    Wv> And I just read that you can always extend the expiration date on an   
    Wv> already expired key, and send that out to the key servers. So there is   
    Wv> no reason to not use an expiration date on keys. I think I'm gona set   
    Wv> mine to 5 years...   
      
   Fair enough :)   
      
   --- Mystic BBS v1.12 A36 (Windows/32)   
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)