Per best practice don't permit PKCS#11 private keys to be modified (fixes #1018). #1020
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(This description has been updated following re-work of the PR as described in the comments below)
This PR adds
krill.conf
configuration settings that give operators control (per #1018) over some of the PKCS#11 attributes set on new public and private keys that Krill creates, rather than assume in Krill that we know what the best defaults / hard-coded values are.The existing default behaviour is preserved for backward compatibility, i.e. these new settings do nothing if not used.