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

Light client voting_power_in can't detect invalid signers #140

Closed
ebuchman opened this issue Feb 2, 2020 · 1 comment · Fixed by #163
Closed

Light client voting_power_in can't detect invalid signers #140

ebuchman opened this issue Feb 2, 2020 · 1 comment · Fixed by #163
Assignees

Comments

@ebuchman
Copy link
Member

ebuchman commented Feb 2, 2020

Follow up to one point in #110:

The voting_power_in method can't detect signatures from validators not in the current validator set. While this isn't really a big deal, since we can't be fooled into accepting something that wasn't correctly signed, there is no good reason for us to receive a commit with a signature from a validator who's not in the validator set, and thus we should be able to detect it and mark the full node we got it from as faulty.

liamsi added a commit that referenced this issue Feb 3, 2020
* validate input for TrustThresholdFraction::new

* minor doc improvements / fix typos etc

* consistent asserts

* add implementation specific checks to mock commit

* delete obsolete vars from tests

* Add note about impl. specif check & err

* Comment about voting_power_in and issue #140

* Consolidate test

* Remove store from JSON tests, add PartialEq to test SH against returned TS

* Remove the store completely

* Fix JSON test

* remove dev-dependency on tendermint-lite

* more readable
@liamsi
Copy link
Member

liamsi commented Feb 5, 2020

Seems related: #143 (comment)

@Shivani912 Shivani912 self-assigned this Feb 27, 2020
This was referenced Feb 27, 2020
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 a pull request may close this issue.

3 participants