gpg expiration date format

[David Shaw]

On Mon, Nov 11, 2002 at 03:52:52PM +0100, Werner Koch wrote:
> On Mon, 11 Nov 2002 07:41:35 -0500, David Shaw said:
> 
> > This would only be for use with GPGME.  With GPGME, the "user" is a
> > program so it probably already has all its times in epoch form so leap
> > seconds, etc, are already resolved.  Perhaps it would be better to
> 
> There is another problem with Epoch which is more real for most
> purposes: time_t is a signed integer and on most systems it is 32 bit,
> this means that it won't work anymore from 2038 on.  This is already
> now a problem because I have seen expiration dates beyond that year
> and for a couple of other applications you are interested in
> years > 2038.

Good point.  2106 is going to be an interesting year as well.  I guess
there is some time before there is a real problem there..

David

-- 
   David Shaw  |  dshaw@jabberwocky.com  |  WWW http://www.jabberwocky.com/
+---------------------------------------------------------------------------+
   "There are two major products that come out of Berkeley: LSD and UNIX.
      We don't believe this to be a coincidence." - Jeremy S. Anderson