X509CRLBuilder and NextPublish extension

[jalliot]

I know CRL extensions modification is on your todo list but there is at least one beside CRLNumber that should be implemented in priority: NextPublish extension.
At the moment, even if we change ThisUpdate and NextUpdate, the original NextPublish extension is not modified or even settable.

I intended to use this new class to generate CRLs in the future but lack of support of the NextPublish means that those generated CRLs would have dates set in the past.
From an API perspective, just add a new NextPublish public property like for ThisUpdate and NextUpdate. If not set AND ThisUpdate/NextUpdate differ from the original CRL, I guess the best would be to remove entirely the extension if it is present.

[Crypt32]

I will take this into consideration. I think the idea with additional property is good enough. But the behavior should be: NULL by default. Do not copy this extension from source CRL and leave it up to API consumer to provide this extension. One more thing: should I validate NextPublish (when presented) whether it is within This and Next update?

[jalliot]

Yes that probably makes even more sense leaving it null by default. And validate its boundaries would be good as well (careful though it could equal to NextUpdate): ThisUpdate < NextPublish <= NextUpdate

[Crypt32]

Fixed in v3.4.1

[Crypt32]

Please, let me know if this works for you as expected.