Monero

This commit changes how Monero stores and loads a list of sensitive multisignature wallet keys. Previously, the code used a generic 'copy the raw bytes' path for a container of secret keys. That generic path could leave copies of secret key bytes in temporary memory or use a copy method not safe for non-trivial types. The patch forces the keys to be converted through an explicitly cleared intermediate type and adds a compile-time guard so the generic blob-copy helper can only be used on simple, safe types. In short: it reduces the chance that secret key material leaks or gets mishandled during wallet serialization.

This commit swaps the two arguments in two calloc() calls so they follow the conventional order (number of elements first, then element size). On standard platforms this produces identical memory allocation results and does not change program behavior or fix any security bug. It only silences compiler warnings.

This commit is a large but straightforward code reorganization. It moves wallet data structures (such as transaction records, address book entries, and settings enums) out of the giant wallet2 module into a new smaller library called wallet2_basic. The existing wallet2 code now references these shared types instead of defining them itself. There is no user-facing behavior change, no new feature, and no obvious security fix or vulnerability introduced in the visible diff.

This commit fixes a privacy gap in Monero's restricted ZeroMQ RPC mode. Before the patch, someone using the --restricted-zmq-rpc option could still see exact times when transactions arrived and were last relayed through the get_transaction_pool ZMQ call. The HTTP restricted mode already hid those timing details, but the ZMQ path did not. The patch adds the same on/off privacy filter to the ZMQ path so restricted callers now get zeroed-out timestamps, matching restricted HTTP behavior. Timing metadata can help an observer deanonymize or trace transactions, so this is a privacy hardening fix.

This commit adds a safety check to a Monero wallet command called rescan_spent. Previously, the command could be run even when the wallet was connected to a daemon it did not trust. The fix now refuses to run the command unless the daemon is marked as trusted. This matters because an untrusted daemon could potentially lie about which coins have been spent, which may confuse the wallet's balance or, in the worst case, be used to manipulate transaction creation.

This commit removes a Windows-only debug assertion helper called LOCAL_ASSERT that was effectively dead code. It does not change how the software handles errors in normal builds, and it does not introduce a security vulnerability.

This commit is a build-system cleanup. It changes how the Monero software finds and links the Unbound DNS library during compilation, switching to a more standard CMake method. There is no direct evidence in the commit that it fixes a security vulnerability in running Monero software.

This commit is a routine build-system cleanup. It removes the Boost Chrono library from the link lists of components that don't actually use it, and adds it to the one component that does. There is no change to program logic, no bug fix, and no security relevance visible in the diff.

This is a code-quality refactor, not a security fix. It replaces an older, heavier C++ scope-cleanup helper with a lighter, modern one. The change touches several parts of the program but does not add or remove any security behavior; it only changes how cleanup actions are expressed internally.

This change makes Monero's HTTP digest authentication code handle failures in the MD5 hashing functions more gracefully. Previously, if OpenSSL's MD5 operations failed (for example, because MD5 was disabled in the cryptographic library), the code would silently continue with invalid or empty hash values, potentially allowing authentication to proceed incorrectly. Now the code checks each hashing step and aborts the authentication attempt cleanly if MD5 cannot be computed.

This is a routine code modernization change. It replaces an older, deprecated Boost networking function called strand.wrap with the newer equivalent bind_executor in two files. There is no indication this fixes a security bug; it simply keeps the code compatible with newer versions of the Boost library.