Issues
- 8
known_bits and kp
#21 opened by fitzjalen - 0
kp is the **known leaked part of the internal eHello!Please explain.I have generated a dummy data file.json 1500 signatures,MSB 4 bit and inserted my Pubkey x,y and r,s there. Should I leave the hash as it is?phemeral nonce** during ECDSA. As this is supposed to be an internal secret, it can be read using a side channel. As it is a protected secret, sometimes we don't get it fully, but only a part, the starting bits, or the last bits. That's the exact purpose of LatticeAttack. If you know the nonce in full, you don't need LatticeAttack, as a simple computation using one signature leads to the private key. But if you only know start (or end) of the nonce for a couple of signatures, then LatticeAttack can provide the secret key.
#29 opened by dmitriy0342 - 2
Video example
#28 opened by smartunia - 10
- 12
- 9
- 1
Cant install fplll?
#27 opened by bane77111 - 1
python3-fpylll
#25 opened by hraleigh - 3
- 5
Keys generated
#23 opened by KrashKrash - 4
K Nonce
#22 opened by KrashKrash - 1
read from file r,s,z
#15 opened by eblanakusok - 0
Average time
#20 opened by KrashKrash - 0
Input More Public Keys in Json
#19 opened by KrashKrash - 1
Creating Signatures
#18 opened by KrashKrash - 1
How many set of signatures needed?
#17 opened by KrashKrash - 1
- 1
public key integer
#14 opened by cloudkeychain - 3
ecdummyrpa ram
#13 opened by cloudkeychain - 1
- 1
ethereum network
#10 opened by ramin1234 - 1
minimum number of signatures
#9 opened by heyanheyan - 3
Hello developer
#7 opened by heyanheyan - 2
To json data converter request. Please.
#5 opened by Hurd8x - 3
- 4
LSB 2bit bias
#2 opened by eychei - 3
What am I doing wrong?
#4 opened by carloseduedu