| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
this will make it easier huge wallets to do so without hitting
random limits (eg, max string size in node).
|
| |
|
|
|
| |
- BP+ support added for Trezor
- old Trezor firmware version support removed, code cleanup
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Implements view tags as proposed by @UkoeHB in MRL issue
https://github.com/monero-project/research-lab/issues/73
At tx construction, the sender adds a 1-byte view tag to each
output. The view tag is derived from the sender-receiver
shared secret. When scanning for outputs, the receiver can
check the view tag for a match, in order to reduce scanning
time. When the view tag does not match, the wallet avoids the
more expensive EC operations when deriving the output public
key using the shared secret.
|
| | |
|
| |\
| |
| |
| | |
ad9fde4 UB: virtual methods in destructor at Trezor (mj-xmr)
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
| |
- Try empty passphrase first when opening a wallet, as all Trezors will have passphrase enabled by default by Trezor Suite by default.
This feature enables easier access to all users using disabled passphrase (or empty passhprase)
- If wallet address differs from device address with empty passphrase, another opening attempt is made, without passphrase suppression,
so user can enter his passhprase if using some. In this scenario, nothing changes to user, wallet opening just consumes one more call
to Trezor (get wallet address with empty passphrase)
- also change how m_passphrase is used. Previous version did not work well with recent passphrase entry mechanism change (made in Trezor),
thus this commit fixes the behaviour).
|
| |\
| |
| |
| | |
a48db50 device_trezor_base: fix typo (anon)
|
| | | |
|
| |\ \
| |/
|/|
| | |
8ae6c85 trezor: add #if for ByteSizeLong (selsta)
|
| | |
| |
| |
| | |
Turns out Ubuntu 18.04 ships with an old protobuf version.
|
| |/
|
|
| |
CID 1446575
|
| |\
| |
| |
| | |
08e4497 Improve cryptonote (block and tx) binary read performance (Lee Clagett)
|
| | | |
|
| |/ |
|
| | |
|
| |\
| |
| |
| | |
68f1ca6 trezor: simplify recognition of integrated addresses (Dusan Klinec)
|
| | |
| |
| |
| |
| | |
now it is possible to simplify integrated addresses recognition using transaction destination info directly
fixes https://github.com/monero-project/monero-gui/issues/3346
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
| |
They are allowed from v12, and MLSAGs are rejected from v13.
|
| |\
| |
| |
| | |
5ef0607da Update copyright year to 2020 (SomaticFanatic)
|
| | |
| |
| |
| | |
Update copyright year to 2020
|
| |\ \
| | |
| | |
| | | |
ab44293 trezor: add new firmware version support (ph4r05)
|
| | |/ |
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
|
| |
- choice where to enter passphrase is now made on the host
- use wipeable string in the comm stack
- wipe passphrase memory
- protocol optimizations, prepare for new firmware version
- minor fixes and improvements
- tests fixes, HF12 support
|
| |
|
|
|
|
|
|
|
| |
- Trezor: support for device address display (subaddress, integrated address)
- Wallet::API support added
- Simplewallet:
- address device [<index>]
- address new <label> // shows address on device also
- integrated_address [device] <payment_id|address> // new optional "device" arg to display also on the device
|
| |
|
|
|
|
|
|
| |
- Trezor type detection refactored, T1 disabled (was enabled before which was a bug)
- Sort connected devices by env TREZOR_PATH
- Compatibility with Trezor ecosystem using TREZOR_PATH env var
- Enables to pick particular Trezor to use in GUI as we don't have the multi-device selection yet
- Dump all detected devices to log for better debugging / troubleshooting
|
| | |
|
| |\
| |
| |
| |
| | |
41901b8d device/trezor: env-configurable ports (Dusan Klinec)
c97a1f79 tests: trezor tests fixes and improvements (Dusan Klinec)
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
c68fe787 device/trezor: add button pressed request (Dusan Klinec)
827f52ad wallet: API changes to enable passphrase entry (Dusan Klinec)
|
| | |/ |
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| |
| | |
c9b13fbb tests/trezor: HF9 and HF10 tests (Dusan Klinec)
a1fd1d49 device/trezor: HF10 support added, wallet::API (Dusan Klinec)
d74d26f2 crypto: hmac_keccak added (Dusan Klinec)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- import only key images generated by cold signing process
- wallet_api: trezor methods added
- wallet: button request code added
- const added to methods
- wallet2::get_tx_key_device() tries to decrypt stored tx private keys using the device.
- simplewallet supports get_tx_key and get_tx_proof on hw device using the get_tx_key feature
- live refresh enables refresh with trezor i.e. computing key images on the fly. More convenient and efficient for users.
- device: has_ki_live_refresh added
- a thread is watching whether live refresh is being computed, if not for 30 seconds, it terminates the live refresh process - switches Trezor state
|
| |\ \
| | |
| | |
| | | |
75e5aafd device/trezor: dummy payment ID fix (Dusan Klinec)
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | | |
1f2930ce Update 2019 copyright (binaryFate)
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | | |
5ea17909 device/trezor: debugging features, trezor tests (Dusan Klinec)
|
| | |/ |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RPC connections now have optional tranparent SSL.
An optional private key and certificate file can be passed,
using the --{rpc,daemon}-ssl-private-key and
--{rpc,daemon}-ssl-certificate options. Those have as
argument a path to a PEM format private private key and
certificate, respectively.
If not given, a temporary self signed certificate will be used.
SSL can be enabled or disabled using --{rpc}-ssl, which
accepts autodetect (default), disabled or enabled.
Access can be restricted to particular certificates using the
--rpc-ssl-allowed-certificates, which takes a list of
paths to PEM encoded certificates. This can allow a wallet to
connect to only the daemon they think they're connected to,
by forcing SSL and listing the paths to the known good
certificates.
To generate long term certificates:
openssl genrsa -out /tmp/KEY 4096
openssl req -new -key /tmp/KEY -out /tmp/REQ
openssl x509 -req -days 999999 -sha256 -in /tmp/REQ -signkey /tmp/KEY -out /tmp/CERT
/tmp/KEY is the private key, and /tmp/CERT is the certificate,
both in PEM format. /tmp/REQ can be removed. Adjust the last
command to set expiration date, etc, as needed. It doesn't
make a whole lot of sense for monero anyway, since most servers
will run with one time temporary self signed certificates anyway.
SSL support is transparent, so all communication is done on the
existing ports, with SSL autodetection. This means you can start
using an SSL daemon now, but you should not enforce SSL yet or
nothing will talk to you.
|