Backport fix mark peer rpcs unsafe#1039
Merged
gilescope merged 2 commits intoMar 19, 2026
Merged
Conversation
Signed-off-by: Giles Cope <gilescope@gmail.com>
Signed-off-by: Giles Cope <gilescope@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Backport of #1027 to
release/node-0.22.1.Marks the
network_peerReputations,network_peerReputation, andnetwork_unbanPeerRPC methods as unsafe so they require--rpc-methods unsafeto be called. This prevents exposing peer reputation data and peer management on public-facing RPC endpoints.Changes
with_extensionstopeerReputationsandpeerReputationRPC method attributescheck_if_safe(ext)?guard to both method implementations