| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
|
| |/
|
|
|
| |
also add a note when receiving the tx, because the user
might not notice the "XXX blocks to unlock" in the balance.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| | |
5ade7281 Wallet API: multisig_tx_set passing bug fixed (naughtyfox)
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | | |
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
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |\
| |
| |
| | |
b8c5f550 wallet api: don't truncate address in subaddress_account (selsta)
|
| | |
| |
| |
| | |
Same behaviour as subaddress.cpp now.
|
| | | |
|
| |\ \
| |/
|/|
| | |
13785ec9 wallet api/device: set estimated restore height if none is provided (selsta)
|
| | | |
|
| |/ |
|
| | |
|
| |\
| |
| |
| | |
a7960542 WalletAPI: rescanBlockchain, rescanBlockchainAsync (mmitkevich)
|
| | | |
|
| | |
| |
| |
| | |
Apparently some people seem to think it's a censorship list...
|
| |/
|
|
|
| |
It was creating a new wallet without a password first (this should
be fixed), then not changing the password correctly
|
| |\
| |
| |
| |
| | |
9acf42d3 Multisig M/N functionality core tests added (naughtyfox)
9f3963e8 Arbitrary M/N multisig schemes: * support in wallet2 * support in monero-wallet-cli * support in monero-wallet-rpc * support in wallet api * support in monero-gen-trusted-multisig * unit tests for multisig wallets creation (naughtyfox)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
* support in wallet2
* support in monero-wallet-cli
* support in monero-wallet-rpc
* support in wallet api
* support in monero-gen-trusted-multisig
* unit tests for multisig wallets creation
|
| | | |
|
| | |
| |
| |
| | |
amount and offset (instead of pubkey)
|
| | |
| |
| |
| | |
921b0fb1 use default create_address_file argument (m2049r)
|
| | |
| |
| |
| | |
a21da905 Wallet: use unique_ptr for WalletImpl members (oneiric)
|
| |/
|
|
| |
7a056f44 WalletAPI: multisigSignData bug fixed (naughtyfox)
|
| | |
|
| | |
|
| |\
| |
| |
| | |
6e6ffc06 wallet2_api: bring up to latest wallet api (moneromooo-monero)
|
| | | |
|
| |\ \
| | |
| | |
| | | |
26971d46 WalletAPI: 'hasMultisigPartialKeyImages' function added (naughtyfox)
|
| | | | |
|
| | |/
|/| |
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The secret spend key is kept encrypted in memory, and
decrypted on the fly when needed.
Both spend and view secret keys are kept encrypted in a JSON
field in the keys file. This avoids leaving the keys in
memory due to being manipulated by the JSON I/O API.
|
| | |
|
| | |
|
| |\
| |
| |
| | |
4307489 wallet: disable core dumps on startup in release mode (moneromooo-monero)
|
| | | |
|
| | | |
|
| |/
|
|
|
| |
Also added notes to WalletManager::verifyWalletPassword (which afaik seems unused
by anyone at the moment) regarding the need to unlock the keys file beforehand.
|
| | |
|
| |\
| |
| |
| | |
4510f41 Wallet API: add some missing override keyword (stoffu)
|