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

Incompatible with OpenDNSSEC 2.1.13 : key handles are not shared between sessions #57

Closed
nponsard opened this issue Jul 25, 2023 · 3 comments · Fixed by #61
Closed

Incompatible with OpenDNSSEC 2.1.13 : key handles are not shared between sessions #57

nponsard opened this issue Jul 25, 2023 · 3 comments · Fixed by #61
Labels
enhancement New feature or request priority: low

Comments

@nponsard
Copy link
Contributor

nponsard commented Jul 25, 2023

If we don't have any answer from the OpenDNSSEC team we would have to change the implementation to have one unique object Db per Token/Slot.

OpenDNSSEC issue : https://issues.opendnssec.org/browse/SUPPORT-286

@nponsard nponsard added enhancement New feature or request priority: low labels Jul 25, 2023
@nponsard nponsard mentioned this issue Jul 25, 2023
@jans23
Copy link
Member

jans23 commented Jul 26, 2023

Can we add an option to support this (which would be disabled by default)?

@nponsard
Copy link
Contributor Author

Adding an option like that would add more complexity in the code.
The mitigation for this problem is to have one single cache per NetHSM/Slot instead of a cache per session. We could just change the cache to be per slot and that would work for every application. The only drawback being that the cache may stay invalid for longer and that could be fixed by a better handling of errors.

@jans23
Copy link
Member

jans23 commented Jul 26, 2023

Sounds fine for me.

@nponsard nponsard linked a pull request Jul 27, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority: low
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants