Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

system: restrict CRL use to one per CA #7015

Closed
2 tasks done
fichtner opened this issue Nov 16, 2023 · 0 comments
Closed
2 tasks done

system: restrict CRL use to one per CA #7015

fichtner opened this issue Nov 16, 2023 · 0 comments
Assignees
Labels
cleanup Low impact changes
Milestone

Comments

@fichtner
Copy link
Member

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Is your feature request related to a problem? Please describe.

Currently multiple CRLs can be created for a CA, but that workflow is unpractical for guessing which CRL may belong to which service. Currently only OpenVPN and OPNWAF use this approach to CRL selection. IPsec needs CRLs too, but we would like to make this simpler.

Describe the solution you like

For now restrict the CRL creation amount per CA to a single CRL, but leave the already created CRLs in place. Maybe mark them as deprecated.

In a later step we could actually merge them into one single CRL. If a CRL is set for a certificate it should be used so IPsec doesn't need a switch but only backend glue to place the CRL. OpenVPN and OPNWAF will lose their ability to select a CRL but will use the one that is there.

Describe alternatives you considered

Leaving the multiple CRL situation, but that has other disadvantages and people are already asking for external CRL providers as well (#6838).

Additional context

N/A

@fichtner fichtner added the cleanup Low impact changes label Nov 16, 2023
@fichtner fichtner added this to the 24.1 milestone Nov 16, 2023
AdSchellevis added a commit that referenced this issue Jan 4, 2024
fichtner pushed a commit that referenced this issue Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cleanup Low impact changes
Development

No branches or pull requests

2 participants