Author | SHA1 | Message | Date |
---|---|---|---|
Adrian Brink | 32311acd01 |
Vulnerability in light client proxy (#1081)
* Vulnerability in light client proxy When calling GetCertifiedCommit the light client proxy would call Certify and even on error return the Commit as if it had been correctly certified. Now it returns the error correctly and returns an empty Commit on error. * Improve names for clarity The lite package now contains StaticCertifier, DynamicCertifier and InqueringCertifier. This also changes the method receivers from one letter to two letter names, which will make future refactoring easier and follows the coding standards. * Fix test failures * Rename files * remove dead code |
7 years ago |
Adrian Brink |
248f176c1f
|
Rename light to lite | 7 years ago |
Adrian Brink |
1871a7c3d0
|
Rename certifier to light (#784) and add godocs
The certifier package is renamed to light. This is more descriptive especially in the wider blockchain context. Moreover we are building light-clients using the light package. This also adds godocs to all exported functions. Furthermore it introduces some extra error handling. I've added one TODO where I would like someone else's opinion on how to handle the error. |
7 years ago |
Ethan Frey | f653ba63bf | Separated out certifiers.Commit from rpc structs | 7 years ago |
Ethan Frey | b4fd6e876e | Copy certifiers from light-client | 7 years ago |