Hello, I sent the following message to openssl-dev, but it didn't seem to receive any interest there.
Would it be possible to review and then apply this patch to the official 0.9.8 and 1.0 branches? - Max ---------- Forwarded message ---------- From: Maxim Khitrov <m...@mxcrypt.com> Date: Tue, Jan 24, 2012 at 8:00 AM Subject: [PATCH] Allow the use of startdate and enddate for ca -gencrl command To: openssl-dev@openssl.org Hi all, The attached patch allows the use of -startdate and -enddate parameters with the 'ca -gencrl' command for directly setting lastUpdate and nextUpdate CRL fields. This is the first time that I needed to modify OpenSSL source code, so while the patch is very simple and works for me, I'd appreciate it if someone more knowledgeable took a look at it. The two date parameters are already available when signing certificate requests, but CRL generation is limited to using -crldays and -crlhours (and -crlsec in 1.0+) for indirectly setting the nextUpdate field. The lastUpdate field is set to the current system time, which isn't always the appropriate choice. I'm trying to schedule CRLs for publication in the future. Changing just the nextUpdate field seems to be insufficient. Firefox, for instance, refuses to update the CRL when the new one uses the same lastUpdate timestamp as the current CRL. The error message is: The application cannot import the Certificate Revocation List (CRL). New CRL is older than the current one. This could be a bug in Firefox, but even so, I think it would be useful to have more direct control over the validity period of the generated CRLs. - Max
openssl-0.9.8-gencrl.patch
Description: Binary data
openssl-1.0.1-gencrl.patch
Description: Binary data
