| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| |
|
|
|
| |
This uses OpenSSL's non-deprecated EVP digest facility to calculate MD5
in HTTP digest authentication.
|
| |\
| |
| |
| | |
008ba966d blockchain sync: reduce disk writes from 2 to 1 per tx (jeffro256)
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | | |
d13da6e71 tests: include <iomanip> where using std::setfill (jeffro256)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
e44e8b164 wallet: background sync with just the view key (j-berman)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- When background syncing, the wallet wipes the spend key
from memory and processes all new transactions. The wallet saves
all receives, spends, and "plausible" spends of receives the
wallet does not know key images for.
- When background sync disabled, the wallet processes all
background synced txs and then clears the background sync cache.
- Adding "plausible" spends to the background sync cache ensures
that the wallet does not need to query the daemon to see if any
received outputs were spent while background sync was enabled.
This would harm privacy especially for users of 3rd party daemons.
- To enable the feature in the CLI wallet, the user can set
background-sync to reuse-wallet-password or
custom-background-password and the wallet automatically syncs in
the background when the wallet locks, then processes all
background synced txs when the wallet is unlocked.
- The custom-background-password option enables the user to
open a distinct background wallet that only has a view key saved
and can be opened/closed/synced separately from the main wallet.
When the main wallet opens, it processes the background wallet's
cache.
- To enable the feature in the RPC wallet, there is a new
`/setup_background_sync` endpoint.
- HW, multsig and view-only wallets cannot background sync.
|
| | |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Correct the unit tests for tools::is_hdd to avoid making assumptions
about the configuration of a particular device based solely on the
value of the __GLIBC__ preprocessor flag. Instead, rely on the
test invoker to provide paths for devices of specific types via
the process environment, thereby avoiding faulty assumptions and
improving the specificity of test assertions. To ensure appropriate
devices exist, add a script, tests/create_test_disks.sh, which
configures loopback devices mirroring relevant configurations.
|
| |\ \
| | |
| | |
| | | |
0cd74568d Cleanup TCP throttling code (performance) + move connection checks (Lee *!* Clagett)
|
| | | | |
|
| | | |
| | |
| | |
| | | |
"example.com" now has more than one A record
|
| |\ \ \
| | | |
| | | |
| | | | |
a1b545a p2p: allow comments in banlist files (jeffro256)
|
| | |/ /
| | |
| | |
| | | |
In-line comments explicitly explaining banned hosts/subnets might help assuage fears of some good banlists' arbitaryiness.
|
| |/ /
| |
| |
| | |
Co-authored-by: Boog900 <boog900@tutanota.com>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
[RELEASE]
1. Use std::is_standard_layout and std::is_trivially_copyable instead of std::is_pod for KV byte-wise serialization, which fixes compile issue for Boost UUIDs
2. Removed reimplementation of std::hash for boost::uuids::uuid
3. Removed << operator overload for crypto::secret_key
4. Removed instances in code where private view key was dumped to the log in plaintext
Release version of #9450, containing C++14 modified assertions
|
| | | |
|
| | |
| |
| |
| |
| | |
Fixes a regression introduced in #9254. Previously it did not
include the dot.
|
| |\ \
| | |
| | |
| | | |
c5ad937 Fix ZMQ DaemonInfo: (Lee *!* Clagett)
|
| | |/
| |
| |
| |
| |
| | |
* top_block_hash was never set in handler
* wide_difficulty was never sent in JSON
* wide_cumulative_difficulty was never sent in JSON
|
| |/
|
|
|
|
|
| |
1. Fix duplicate transaction #9335
2. Add test for cases where there are duplicate transaction in fluff
Co-authored-by: Boog900 <boog900@tutanota.com>
|
| |\
| |
| |
| | |
dd47d03 Enforce Tx unlock_time is Zero by Relay Rule [RELEASE] (jeffro256)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Related to https://github.com/monero-project/research-lab/issues/78
Added a relay rule that enforces the `unlock_time` field is equal to 0 for non-coinbase transactions.
UIs changed:
* Removed `locked_transfer` and `locked_sweep_all` commands from `monero-wallet-cli`
APIs changed:
* Removed `unlock_time` parameters from `wallet2` transfer methods
* Wallet RPC transfer endpoints send error codes when requested unlock time is not 0
* Removed `unlock_time` parameters from `construct_tx*` cryptonote core functions
@tobtoht: undo rebase changes tx.dsts -> tx_dsts
|
| |\ \
| | |
| | |
| | | |
755dddd common: support boost filesystem copy_options. Co-authored-by: selsta <selsta@sent.at> (0xFFFC0000)
|
| | |/
| |
| |
| | |
Co-authored-by: selsta <selsta@sent.at>
|
| |/ |
|
| | |
|
| |\
| |
| |
| | |
33e3f72 serialization: fix infinite loops and clean up dispatching (jeffro256)
|
| | |
| |
| |
| | |
Resolves #8687
|
| |\ \
| | |
| | |
| | | |
f5b8634 Add <cstdint> to aligned test (Lee *!* Clagett)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
98ee46f Disable/fix ports with I2P (Lee Clagett)
|
| | |/ |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To transfer ~5 XMR to an address such that your balance drops by exactly 5 XMR, provide a `subtractfeefrom` flag to the `transfer` command. For example:
transfer 76bDHojqFYiFCCYYtzTveJ8oFtmpNp3X1TgV2oKP7rHmZyFK1RvyE4r8vsJzf7SyNohMnbKT9wbcD3XUTgsZLX8LU5JBCfm 5 subtractfeefrom=all
If my walet balance was exactly 30 XMR before this transaction, it will be exactly 25 XMR afterwards and the destination address will receive slightly
less than 5 XMR. You can manually select which destinations fund the transaction fee and which ones do not by providing the destination index.
For example:
transfer 75sr8AAr... 3 74M7W4eg... 4 7AbWqDZ6... 5 subtractfeefrom=0,2
This will drop your balance by exactly 12 XMR including fees and will spread the fee cost proportionally (3:5 ratio) over destinations with addresses
`75sr8AAr...` and `7AbWqDZ6...`, respectively.
Disclaimer: This feature was paid for by @LocalMonero.
|
| |\
| |
| |
| | |
47d8899 Fix missing checks for IsObject in ZMQ jsonrpc reading (Lee Clagett)
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
Co-authored-by: j-berman <justinberman@protonmail.com>
|
| | |
|
| |\
| |
| |
| | |
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.
|