-
Notifications
You must be signed in to change notification settings - Fork 115
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
go/oasis-node/cmd: Allow using non local gRPC connections #4617
Conversation
f014f05
to
4fed149
Compare
Codecov Report
@@ Coverage Diff @@
## master #4617 +/- ##
==========================================
- Coverage 67.17% 67.02% -0.15%
==========================================
Files 430 430
Lines 48666 48671 +5
==========================================
- Hits 32690 32624 -66
- Misses 11964 12017 +53
- Partials 4012 4030 +18
Continue to review full report at Codecov.
|
Ultimately I don't see the point of this. The only time when this really is an issue is when voting on governance, and the current voting period which ends in a day should be the last governance vote where this tooling needs to be used in the first place. tldr; use the sdk-cli. If the sdk-cli doesn't provide what you need, go add to it. |
4fed149
to
772b2f3
Compare
I agree that the future of CLI tooling is to migrate to the new Oasis CLI we are developing in the Oasis SDK repo but I think this small change will still improve the UX until people migrate to that. Another example where this would have impact is that people who don't have access to a synced node would like to use State Sync and need the list of nodes that offer that. With this change, they could use:
|
Require server-side TLS for non unix-socket gRPC connections.
772b2f3
to
474266c
Compare
Require server-side TLS for non unix-socket gRPC connections.