We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I would like to transfer the following issue to the rusty-kaspa repo:
rusty-kaspa
Currently, many nodes have RPC ports potentially open to the world Some manner of authentication should be implemented to mitigate it Suggested solution: gRPC supports authentication out-of-the-box: https://grpc.io/docs/guides/auth/
Currently, many nodes have RPC ports potentially open to the world Some manner of authentication should be implemented to mitigate it
Suggested solution: gRPC supports authentication out-of-the-box: https://grpc.io/docs/guides/auth/
Source: kaspanet/kaspad#1893
Only the auth method should probably ideally support wRPC, gRPC and all potential future protocols in a generic manner.
The text was updated successfully, but these errors were encountered:
As per the original issue; it is preferable if the auth of a connection can be handled on a per call / notfification basis.
Sorry, something went wrong.
It should be handled by proxies, reference sofwares should be simple as much as possible i think
Starting to figure this out now
No branches or pull requests
I would like to transfer the following issue to the
rusty-kaspa
repo:Source: kaspanet/kaspad#1893
Only the auth method should probably ideally support wRPC, gRPC and all potential future protocols in a generic manner.
The text was updated successfully, but these errors were encountered: