Skip to content
New issue

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

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

Already on GitHub? # to your account

Update unbound DNS for openssl 3.x.x #220

Closed
wants to merge 1 commit into from

Conversation

ryndia
Copy link
Contributor

@ryndia ryndia commented Jul 24, 2023

this update used the latest openssl oqs provider as recommended.

this update used the latest openssl oqs provider as recommended.
Copy link
Member

@baentsch baentsch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks very much for this update, @ryndia . It all builds OK but without a CI run (#171) I cannot really judge whether all works as desired. When reading through the documentation, I wonder about this: https://github.com/open-quantum-safe/oqs-demos/blob/main/unbound/USAGE-client.md#usage: It refers to (oqs-)BoringSSL for the selection of algorithms: Is this intentional? Shouldn't the reference rather go to https://github.com/open-quantum-safe/oqs-provider#algorithms? Worthwhile updating the PR?

@ryndia
Copy link
Contributor Author

ryndia commented Jul 24, 2023

Thanks very much for this update, @ryndia . It all builds OK but without a CI run (#171) I cannot really judge whether all works as desired. When reading through the documentation, I wonder about this: https://github.com/open-quantum-safe/oqs-demos/blob/main/unbound/USAGE-client.md#usage: It refers to (oqs-)BoringSSL for the selection of algorithms: Is this intentional? Shouldn't the reference rather go to https://github.com/open-quantum-safe/oqs-provider#algorithms? Worthwhile updating the PR?

ok I will update the pr to join both docker file and update the usage readme, i forgot this instruction in the usage readme. thank you

@baentsch
Copy link
Member

@ryndia May I ask when (whether) you'll have time to conclude this?

@baentsch
Copy link
Member

Closing due to no activity.

@baentsch baentsch closed this Mar 20, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants