Replies: 3 comments 8 replies
|
I think Tonic is the best choice here:
Auth can be handled with an
It includes TLS via rustls.
This could be checked in an interceptor for those routes.
The self-signed certificate needed for TLS should work here if I understand this correctly.
The provided transport can accept http1, and it should be possible to write our own server so it can be used via Tor. https://docs.rs/tonic/latest/tonic/transport/server/struct.Server.html#method.accept_http1 Advantages
Drawbacks
|
6 replies
|
@arya2 have you managed to do any additional research on whether we might want to use any other libraries for authentication? |
2 replies
|
We're not going to do any further work on the scanner |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Let's use this discussion to evaluate various different RPC libraries against our requirements.
Requirements
Security requirements
Other requirements
Let's add each potential library as a new comment and add the evaluation against the criteria as comments under each library
All reactions