-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello,

last year i created my keys, certs and so on with the following steps:

openssl req -new -x509 -newkey rsa:2048 -keyout ssl_priv.pem -out
ca_cert.pem -days 3650 -config ./openssl.conf

openssl x509 -in ca_cert.pem -out ca_cert.crt

openssl genrsa -out serverkey.pem -aes128 2048 -days 3650 -config
./openssl.conf

openssl req -new -key serverkey.pem -out req.pem -nodes -config
./openssl.conf

openssl ca -keyfile ssl_priv.pem -cert ca_cert.pem -in req.pem -notext
- -out servercert.pem -config ./openssl.conf


And today my certificate is invalid, cause due an "error" the
servercert.pem is only valid 365 days. It should be 3650 days.

With the following commands
openssl req -new -keyout clients/client-key-XXXXX.pem -out
clients/client-req-XXX.pem -days 365 -config ./openssl.conf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJTHG1CAAoJEFF6fE6T32A8QuQIAJ3Kne9DqMtKiGLUWzLr3zw2
KqzCYpD2ZjijdRur3WDYUuFrWO+4xs+lKCKKMTjMh1gy1MJuCjNYf2iyVLiWtgx9
1ClGDnXoMc1b6HKBgx0v1dZJEpfT1tBn8k/rdfc17aRNaUiNOTxz0OhyDi891Xbj
xgBiNWmw9ercAJ4Mms9RTF/KSesxWKMZbqN4FQ8PQ/6YPEpOdeP/zcgn4xT1Qj4Z
cpO0o9cb8lhk/pP4dVNi5nuNbspU07/nsZuTKU7wQ7pJTsJ0D2QYopx1Bu/QscQ8
810Tnd2O/DmkFJi+xueN7Nw/Ff18Xuh1OYh54Cbtp2Vy2Rp9V0MCt/ti0ahNG/w=
=hbXh
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Openvpn-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openvpn-users

Reply via email to