| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| |
| | |
7dbb14b functional_tests: fix multisig tests noutputs assertion (jeffro256)
|
| | |
| |
| |
| | |
The changes to the multisig tests in #8914 and #8904 affected each other, this PR cleans up the code and fixes that issue.
|
| |/
|
|
|
|
|
|
| |
Resolves #8932 and:
2. Not storing cache when new path is different from old in `store_to()` and
3. Detecting same path when new path contains entire string of old path in `store_to()` and
4. Changing your password / decrypting your keys (in this method or others) and providing a bad original password and getting no error and
5. Changing your password and storing to a new file
|
| |\
| |
| |
| | |
78348bc wallet-rpc: restore from multisig seed (jeffro256)
|
| | | |
|
| |\ \
| |/
|/|
| | |
842478c core_rpc_server: return ID of submitted block (jeffro256)
|
| | | |
|
| |\ \
| | |
| | |
| | | |
dc24312 wallet: respect frozen key images in multisig wallets [RELEASE] (jeffro256)
|
| | |/
| |
| |
| |
| |
| |
| | |
Before this change, if a multisig peer asked you to sign a transaction with a frozen enote, the wallet will do it without any error or warning. This change makes it
so that wallets will refuse to sign multisig transactions with frozen enotes.
Disclaimer: This PR was generously funded by @LocalMonero.
|
| |\ \
| | |
| | |
| | | |
8dc4abd common: do not use DNS to determine if address is local (tobtoht)
|
| | |/
| |
| |
| | |
Co-authored-by: j-berman <justinberman@protonmail.com>
|
| |\ \
| |/
|/|
| | |
65e13db wallet2: fix rescanning tx via scan_tx (j-berman)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Detach & re-process txs >= lowest scan height
- ensures that if a user calls scan_tx(tx1) after scanning tx2,
the wallet correctly processes tx1 and tx2
- if a user provides a tx with a height higher than the wallet's
last scanned height, the wallet will scan starting from that tx's
height
- scan_tx requires trusted daemon iff need to re-process existing
txs: in addition to querying a daemon for txids, if a user
provides a txid of a tx with height *lower* than any *already*
scanned txs in the wallet, then the wallet will also query the
daemon for all the *higher* txs as well. This is likely
unexpected behavior to a caller, and so to protect a caller from
revealing txid's to an untrusted daemon in an unexpected way,
require the daemon be trusted.
|
| |/ |
|
| |\
| |
| |
| | |
2c24322 DNSResolver: fix not handling hostnames without dot characters [release] (Jeffrey Ryan)
|
| | |
| |
| |
| | |
Unrelated, but similar code-wise to #8643. There is a check in `DNSResolver` which automatically fails to resolve hostnames which do not contain the `.` character. This PR removes that check.
|
| |\ \
| | |
| | |
| | | |
38d4811 p2p: fix exclusive node DNS resolution for certain hosts [release] (Jeffrey Ryan)
|
| | |/
| |
| |
| |
| |
| |
| |
| | |
Fixes #8633. The function `append_net_address` did not parse hostname + port addresses (e.g. `bar:29080`) correctly if the hostname did not contain a `'.'` character.
@vtnerd comments 1
clear up 2nd conditional statement
|
| |/ |
|
| |\
| |
| |
| | |
802c4bb Move update_checkpoints() to a later stage (SChernykh)
|
| | |
| |
| |
| | |
update_checkpoints() makes a few DNS requests and can take up to 20-30 seconds to complete (3-6 seconds on average). It is currently called from core::handle_incoming_block() which holds m_incoming_tx_lock, so it blocks all incoming transactions and blocks processing while update_checkpoints() is running. This PR moves it to until after a new block has been processed and relayed, to avoid full monerod locking.
|
| |\ \
| | |
| | |
| | | |
1cd21bf add an option to force-update multisig key exchange under some circumstances (koe)
|
| | |/ |
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
12e7c41 Merge pull request #5 from j-berman/restore-msig-encrypted-seed (Justin Berman)
848a0c0 Fix segfault restoring encrypted multisig seed (j-berman)
401f5d9 Require user ack multisig is experimental to restore (j-berman)
fc8a5d6 multisig: fix #8537 seed restore (suggestions by @UkoeHB) (j-berman)
|
| | |
| |
| |
| |
| |
| |
| |
| | |
- spend secret key is no longer the sum of multisig key shares;
no need to check that is the case upon restore.
- restoring a multisig wallet from multisig info means that the
wallet must have already completed all setup rounds. Upon restore,
set the number of rounds completed accordingly.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Being offline is not a good enough heuristic, so we keep track
of whether the wallet ever refreshed from a daemon, which is a
lot better, and probably the best we can do without manual user
designation (which would break existing cold wallet setups till
the user designates those wallets)
|
| | |
| |
| |
| |
| | |
this will make it easier huge wallets to do so without hitting
random limits (eg, max string size in node).
|
| |/
|
|
|
|
| |
- only allow offline wallets to import outputs
- don't import empty outputs
- export subaddress indexes when exporting outputs
|
| |\
| |
| |
| | |
6075be9 feat(trezor): add HF15 support, BP+ (Dusan Klinec)
|
| | |
| |
| |
| |
| | |
- BP+ support added for Trezor
- old Trezor firmware version support removed, code cleanup
|
| |/ |
|
| |\
| |
| |
| |
| |
| | |
a82fba4 address PR comments (j-berman)
3be1dbd connection: fix implementation (anon)
724ff21 connection: add segfault and deadlocks demo (anon)
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
key images
|
| |/ |
|
| |\
| |
| |
| |
| | |
08080df unit_tests: add more sha256sum test cases (Jeffrey Ryan)
a66a52d common: update sha256sum to use OpenSSL 3.0 API (Jeffrey Ryan)
|
| | | |
|
| |\ \
| | |
| | |
| | | |
2dab31f Don't exclusively drop tor/i2p outgoing cxns in idle loop (j-berman)
|
| | |/ |
|
| |/
|
|
|
|
|
|
|
| |
There are vulnerabilities in multisig protocol if the parties do not
trust each other, and while there is a patch for it, it has not been
throroughly reviewed yet, so it is felt safer to disable multisig by
default for now.
If all parties in a multisig setup trust each other, then it is safe
to enable multisig.
|
| |\
| |
| |
| | |
0226df9 More tests for view tags (SChernykh)
|
| | |
| |
| |
| | |
P2Pool can create transactions with more than 128 outputs, which make output_index's varint larger than 1 byte. Added this test case.
|
| |\ \
| | |
| | |
| | | |
41da2fe Update copyright to 2022 for Hardfork files (Akrit)
|
| | |/
| |
| |
| | |
Update Makefile and LICENSE
|
| |\ \
| | |
| | |
| | | |
baee2c0 Preserve commitment format inside transactions (kayabaNerve)
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | | |
0d6ecb1 multisig: add post-kex verification round to check that all participants have completed the multisig address (koe)
|