-
Notifications
You must be signed in to change notification settings - Fork 0
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
e2e-crypto #1
e2e-crypto #1
Conversation
Co-authored-by: ThetaSinner <[email protected]>
|
||
// Mutex strategy in this file is built on the assumption that this will | ||
// largely be network bound. Since we only have the one rate-limited connection | ||
// to the sbd server, it is okay to wrap it with a tokio Mutex and do the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
std mutex?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do use a std mutex in the sodoken_crypto module, but in this case I'm talking about the tokio mutexes around the inner and receiver because they need to be held across await
s.
DEPENDS ON: #2
RESOLVES: #19
Adds a libsodium secretstream-based p2p-e2e encryption wrapper for the sbd client.