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.

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

Remove account and config RPC calls from TCP #892

Merged
merged 1 commit into from
Jan 14, 2022
Merged

Conversation

NullSoldier
Copy link
Contributor

@NullSoldier NullSoldier commented Jan 14, 2022

Summary

This removes RPC routes in the accounts and config namespace from being
mounted in the TCP adapter. This is to prevent a an attack where
users can have their graffiti changed. This is a short term fix because
the real fix is to add RPC token authentication.

Accessing one of these routes via TCP will now display the following error

No route found config/getConfig in namespace config for method getConfig

Testing Plan

Tested lcoally

Breaking Change

Is this a breaking change? If yes, add notes below on why this is breaking and
what additional work is required, if any.

[ ] Yes
[ ] No

This removes RPC routes in the accounts and config namespace from being
mounted in the TCP adapter. This is to prevent a an attack where
users can have their graffiti changed. This is a short term fix because
the real fix is to add RPC token authentication.

Accessing one of these routes now with TCP will display one of the
following errors.
@NullSoldier NullSoldier merged commit 0b564a3 into staging Jan 14, 2022
@NullSoldier NullSoldier deleted the tcp-namespace branch January 14, 2022 21:15
NullSoldier added a commit that referenced this pull request Jan 15, 2022
This removes RPC routes in the accounts and config namespace from being
mounted in the TCP adapter. This is to prevent a an attack where
users can have their graffiti changed. This is a short term fix because
the real fix is to add RPC token authentication.

Accessing one of these routes now with TCP will display one of the
following errors.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants