f970056a92
Detected during my audit, right before fuzzing, the code that checked for presence of hyphens per path segment assumed that the part would always be non-empty. However, with paths such as: * m/4/ * /44/ * m/4/// it'd panic with a runtime slice out of bounds. With this new change, we now: * firstly strip the right trailing slash * on finding any empty segments of a path return an error Fixes #8557 |
||
|---|---|---|
| .. | ||
| codec | ||
| hd | ||
| keyring | ||
| keys | ||
| ledger | ||
| types | ||
| armor_test.go | ||
| armor.go | ||
| bcrypt_readme.md | ||