Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I tried to gernerate my own root CA with a validity of 40 years as follow: openssl req -new -newkey rsa:4096 -x509 -days 10950 -extensions v3_ca -keyout myca.key -out myca.crt -config /etc/ssl/openssl.cnf

So far so good, finally let's take a look at the certificate with openssl x509 -noout -text -in myca.crt:

   Signature Algorithm: sha1WithRSAEncryption
    Issuer: C=DE, ST=Berlin, L=Berlin, O=Org, OU=Unit, CN=My Root CA/
        Not Before: Jan 31 14:07:06 2012 GMT
        Not After : Dec 18 07:38:50 1905 GMT

Why is the valid to date (not after date) wrong in the certificate? And what can be done to correct this?

Some testing showed, that the overflowing occurs somewhere in January 2038..

share|improve this question
I noticed that too, but on another platform: pfSense 2.x GUI. When creating a CA with a lifetime above 30y the expiration date will be 1.1.1970. Just to say this might be a generic OpenSSL bug/feature. – weeheavy Jan 31 '12 at 14:47
up vote 5 down vote accepted

Found the problem: (keywords "openssl time_t 32bit")

The "fix" in my opinion is to generate your CA on a system with 64-bit OpenSSL.

share|improve this answer
i've just created my cert on a 64-bit OS :-) – JMW Feb 6 '12 at 10:24

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.