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

DNSCrypt: Store the computed shared key and reuse it for the response #4813

Merged
merged 3 commits into from Jan 19, 2017

Conversation

@rgacogne
Copy link
Member

@rgacogne rgacogne commented Dec 23, 2016

Short description

Instead of computing the shared-key derived from the public and private keys twice -when decrypting the query and when encrypting the response- we now store and reuse the shared key.

Checklist

I have:

rgacogne added 3 commits Dec 23, 2016
Instead of computing the shared-key derived from the public and private
keys twice -when decrypting the query and when encrypting the response-
we now store and reuse the shared key.
The documentation states that `sodium_munlock()` will properly zero
the memory before making it swappable, so we don't need to call
`sodium_memzero()` ourselves.
@rgacogne rgacogne added this to the dnsdist-1.2.0 milestone Dec 23, 2016
@rgacogne rgacogne merged commit aaa3150 into PowerDNS:master Jan 19, 2017
1 check passed
1 check passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@rgacogne rgacogne deleted the rgacogne:dnscrypt-after-nm branch Jan 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

1 participant