You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Pwnable/400-InsaneInTheBlockchain/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,10 +33,10 @@ Two possible approaches
33
33
* Reverse engineer the binary and find out the value of k
34
34
* Fetch the [geth source code](https://github.com/ethereum/go-ethereum/wiki/geth)
35
35
* Find out which function generates k and work from there (using dynamic or static RE)
36
-
* Google "ecdsa k reuse". Use [this tool](https://github.com/tintinweb/ecdsa-private-key-recovery) and plug in known k (no need for two signatures).
36
+
* Google "ecdsa k reuse". Use [this tool](https://github.com/tintinweb/ecdsa-private-key-recovery) and plug in known k (no need for two signatures)
37
37
38
38
* Analytical method
39
39
* Perform two signatures with some key
40
40
* Google "edsa k reuse". Use [this tool](https://github.com/tintinweb/ecdsa-private-key-recovery)
41
-
* Alternatively, having a known key allows us to extract `k` directly. Having `k` allows us to extract the private key from only transaction only (check out the [solution file](../blob/master/Pwnable/P400-InsaneInTheBlockChain/solution/solution.py)
41
+
* Alternatively, having a known key allows us to extract `k` directly. Having `k` allows us to extract the private key from only transaction only. Check out the [solution file](../blob/master/Pwnable/P400-InsaneInTheBlockChain/solution/solution.py)
0 commit comments