| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |\
| |
| |
| | |
878c781 zmq: apply restricted-mode privacy filtering to get_transaction_pool (greatjourney589)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add an include_sensitive parameter to tx_memory_pool::get_pool_for_rpc
(and its core passthrough), mirroring the include_sensitive_data
parameter on the HTTP analog get_transactions_and_spent_keys_info.
When false, receive_time and last_relayed_time are zeroed using the
same masking already applied on the HTTP path.
The ZMQ handler in daemon_handler.cpp passes !m_restricted, so
--restricted-zmq-rpc callers now receive the same privacy-filtered view
as restricted HTTP callers instead of the unfiltered timing metadata
they previously got. Stem-phase txs continue to be excluded regardless
(relay_category::broadcasted filter unchanged).
Refs #10529.
|
| |\ \
| | |
| | |
| | | |
6bc3784 fix: TypeError: 'method' object is not subscriptable (SNeedlewoods)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
93d792e net: canonicalize Tor/I2P hosts during deserialization (selsta)
|
| | |/ |
|
| | | |
|
| |/ |
|
| |\
| |
| |
| | |
5422919 Improve unpack reserve handling (Lee Clagett)
|
| | | |
|
| |\ \
| | |
| | |
| | | |
44412d3 cryptonote_core: add change address sanity check (jeffro256)
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Prevents silly mistakes where wrong change address is passed
Release versions uses boost::optional instead of std::optional
|
| |/ / |
|
| |\ \
| | |
| | |
| | | |
ce5437f Add Socks v5 support to daemon and wallet (Lee *!* Clagett)
|
| | | |
| | |
| | |
| | | |
(cherry picked from commit 23e29a5074f01cbb781f7e76b0c17ad2b6797af0)
|
| |\ \ \
| |/ /
|/| |
| | | |
1d2ae21 p2p: isolate regtest from mainnet bootstrap state (Jeetraj)
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | | |
017c902 Cleanup some of the fragmented levin handling (Lee *!* Clagett)
|
| | |/ / |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
7f2cfe9 zmq: add restricted rpc mode (selsta)
dd0fb6c daemon: warn user on specifiying ZMQ args with --no-zmq (jeffro256)
|
| | |/ |
|
| |/ |
|
| |
|
|
|
|
|
| |
- Make sure the server sends a complete response when the client
includes the "Connection: close" header.
- Make sure the server terminates in `m_strand` to avoid
concurrent socket closure and ops processing.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Without this commit:
1) read height from DB
2) add block to chain in separate thread
3) read chain for block id's and request them from peer
4) ERR in handle_response_chain_entry, peer's first block is the
one that was added to the chain, which has block idx=height from
step 1.
This commit reads the chain for height and highest block id's
in one go while holding the m_blockchain_lock to avoid the race.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Make sure to mark identified spends in the pool as spends. The
wallet might not know these have been spent if it wasn't the wallet
that relayed the tx to the daemon, or the wallet was cleared via
rescan_bc.
- Make sure to add spends to m_unconfirmed_txs if not present.
- Make sure to process the entire pool again if refreshing for
the first time. The wallet fetches pool and blocks at the same
time. The wallet scans blocks first, then pool. If the wallet
identifies received outputs in the chain, then it may have spent
those received outputs in the pool. So we make sure to re-process
the entire pool again after scanning the chain for the first time.
- Multisig wallets that know about spent key images can now detect
spend txs in the pool. Update tests for that.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
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)
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
13ff355cf Set response limits on http server connections (Lee *!* Clagett)
89fa3ed68 epee: update 'http_server_handlers_map2.h' macros to use fully qualified names (Jeffrey Ryan)
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
Reduce the likelihood of false positive failures in the p2p
transaction propagation functional test by waiting up to a
maximum timeout for a transaction to propagate, rather than using a
fixed timeout, to reflect the random delay of Dandelion++ transaction
propagation. This strategy also speeds test execution in cases where
propagation occurs faster than the previously expected fixed delay.
|
| |\ \
| | |
| | |
| | | |
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>
|