cmake-rewrite
master
dev-v0.11.2
cake-fixes
release-v0.11.1
release-v0.11.0.3
release-v0.10.2
wowletify
release-v0.10.1.1
release-v0.10.1.0
release-v0.10.0.3
release-v0.9.3.3
release-0.8.0.2
release-v0.7.1.0
release-v0.6.1.2
release-v0.5.1
release-v0.5.0
release-v0.4.0.1
release-v0.3.0.0
release-v0.2.2.0
release-v0.2.1.0
v0.11.1.0
v0.11.0.3
v0.11.0.1
v0.11
v0.10.2.1
v0.10.2.0
v0.10.1.0
v0.10.0.3
v0.10.0.2
v0.10.0.1
v10
v0.9.0.2
v0.9.0.1
v0.2.2.0
Busty-Brazzers
v0.2.0.0
alpha
wowhero
v0.9.3.3
v0.9.3.2
v0.9.3.1
v0.9.3.0
v0.9.2.2
v0.9.2.1
v0.9.2.0
v0.9.1.0
v0.9.0.0
v0.8.0.2
v0.8.0.1
v0.8.0.0
v0.7.0
v0.6.1.2
v0.6.1.1
v0.6.1.0
v0.6.0.0
v0.5.1.0
v0.5.0.2
v0.5.0.0
v0.4.0.0
v0.3.1.4
v0.3.1.3
v0.3.1.2
v0.3.1.1
v0.3.1.0
v0.3.0.0
v0.2.2.00
v0.2.1.0
v0.11.0.0
v0.10.0.0
v0.1.0.0
10.0.0
${ noResults }
1 Commits (3edef51d708e1235add4a453b7c51943d133004e)
Author | SHA1 | Message | Date |
---|---|---|---|
cslashm | e745c1e38d |
Code modifications to integrate Ledger HW device into monero-wallet-cli.
The basic approach it to delegate all sensitive data (master key, secret ephemeral key, key derivation, ....) and related operations to the device. As device has low memory, it does not keep itself the values (except for view/spend keys) but once computed there are encrypted (with AES are equivalent) and return back to monero-wallet-cli. When they need to be manipulated by the device, they are decrypted on receive. Moreover, using the client for storing the value in encrypted form limits the modification in the client code. Those values are transfered from one C-structure to another one as previously. The code modification has been done with the wishes to be open to any other hardware wallet. To achieve that a C++ class hw::Device has been introduced. Two initial implementations are provided: the "default", which remaps all calls to initial Monero code, and the "Ledger", which delegates all calls to Ledger device. |
6 years ago |