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.

Sign up for GitHub

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

Jump to bottom

Use libsodium's defined asymmetric encryption scheme instead of RSA #22

Open
ymarcus93 opened this issue Apr 18, 2020 · 1 comment
Open

Use libsodium's defined asymmetric encryption scheme instead of RSA #22

ymarcus93 opened this issue Apr 18, 2020 · 1 comment
Assignees
@ymarcus93
Labels
enhancement New feature or request

Comments

@ymarcus93
Copy link
Owner

Currently, we use the RSA library provided by the standard library in Go. However, the Callisto paper mentions using libsodium for doing asymmetric encryption with the DLOCs and LOCs. Details of the scheme used can be found here: https://libsodium.gitbook.io/doc/public-key_cryptography/authenticated_encryption

Transitioning to this scheme would require instantiating a public DH value for the client, as well as the DLOCs and LOCs.
@ymarcus93 ymarcus93 added the enhancement New feature or request label Apr 18, 2020
@ymarcus93 ymarcus93 self-assigned this Apr 18, 2020
@ymarcus93
Copy link
Owner Author

Alternatively, use the sealed box approach so that Client does not need to manage private DH secrets

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ymarcus93 ymarcus93

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ymarcus93