-
Notifications
You must be signed in to change notification settings - Fork 671
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
Fix/StackerDB Audit #4821
Fix/StackerDB Audit #4821
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Think missed a change in neon_node.rs (caught by github), but aside from that LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good to me, just need to fix the issue preventing the tests from running.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This addresses all of the points brought forth by a StackerDB audit. None of them are security risks or pose a serious problem to the system's operation, so it's safe to just open it against
develop
for now without doing a hotfix.The fixes are:
hint-replicas
in the StackerDB config contractmax-neighbors
to the locally-configurednum_neighbors
inConnectionOptions