adds feature-gate code to enforce retransmitter signature verification#1840
Conversation
8abd1d5 to
3c11dfb
Compare
3c11dfb to
761f5fe
Compare
There was a problem hiding this comment.
LGTM.
The last step is then for replay to check if the last FEC set is of the resigned variant when this feature flag is turned on, similar to
agave/ledger/src/blockstore.rs
Line 3691 in 9ee36fa
Or would we prefer to wait until the resigned variant is turned on, and discard any shred that is not resigned, similar to how we discard legacy shreds, which skips us having to check during replay.
I don't think that would work. So I think we actually need to do what you described earlier:
|
|
Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis. |
Problem
Need to verify if the shred is retransmitted by the expected parent node in Turbine tree.
Summary of Changes
Added feature-gate code to enforce retransmitter signature verification