Note that the actual secret spending key may be leaked.
This commit is contained in:
parent
2b5c33e101
commit
35b3168d2c
|
@ -22,9 +22,10 @@ This implementation of Zcash is not resistant to side-channel attacks. You
|
||||||
should assume other unprivileged users running on the same hardware as your
|
should assume other unprivileged users running on the same hardware as your
|
||||||
`zcashd` process will be able to:
|
`zcashd` process will be able to:
|
||||||
|
|
||||||
- Determine which note your are spending by observing cache side-channels as you
|
- Determine the values of your secret spending keys, as well as which notes you
|
||||||
perform a JoinSplit operation. This is due to probable side-channel leakage in
|
are spending, by observing cache side-channels as you perform a JoinSplit
|
||||||
the libsnark proving machinery.
|
operation. This is due to probable side-channel leakage in the libsnark
|
||||||
|
proving machinery.
|
||||||
|
|
||||||
- Determine which notes you own by observing cache side-channel information
|
- Determine which notes you own by observing cache side-channel information
|
||||||
leakage from the incremental witnesses as they are updated with new notes.
|
leakage from the incremental witnesses as they are updated with new notes.
|
||||||
|
|
Loading…
Reference in New Issue