monero-java

This commit only updates generated Javadoc HTML documentation files. It does not change any source code, runtime behavior, or security logic. The visible differences are documentation additions for existing wallet API methods (such as trusted-daemon flags and key-image import/export) and regenerated index files. There is no security-relevant code change to assess.

This commit changes how a Monero wallet library requests data when signing transactions via RPC. It now explicitly asks the remote wallet to also return the raw transaction hex data and the transaction keys, matching behavior already present in the JNI wallet implementation. There is no direct evidence in the commit that this introduces a security vulnerability; it appears to be a parity/feature completeness change.

This commit adds a new option for users to explicitly tell a Monero wallet whether its connected daemon should be treated as 'trusted.' A trusted daemon can receive more sensitive data or perform more powerful operations than an untrusted one. The change is a feature addition that exposes an existing underlying wallet capability; it does not by itself create a vulnerability, but it makes it easier for users to accidentally or intentionally mark a remote daemon as trusted. That could increase the impact of other attacks if a user is tricked into trusting a malicious daemon.

This commit only changes a test file to fix a flaky test. The test was requesting a reserve proof for an amount slightly above a single account's balance, but the underlying Monero wallet validates against a stricter 'whole-wallet' balance that includes pending-spent outputs. Because unconfirmed transactions can make the strict balance higher than the reported account balance, the old test sometimes failed to trigger the expected error. The fix requests an amount above the whole-wallet balance instead. There is no change to production code, no security vulnerability, and no user-facing behavior change.

This commit simply removes two comment lines in test code that said certain tests occasionally crashed on Apple Silicon Macs. No actual code behavior was changed, so it does not introduce or fix a security issue on its own. It only updates internal notes about previously observed test failures.

This commit only changes a test file. It updates how a Monero wallet test checks transaction destinations: instead of comparing each destination in the exact order it was sent, it now adds up the amounts sent to each address and compares the totals. This is a test-only adjustment to match how the upstream Monero software actually behaves, not a fix for a security problem in production code.

This commit changes one line in a test file. It fixes a test that checks sending Monero from multiple subaddresses in a single, unsplit transaction. Previously the test passed null (likely allowing default split behavior); now it explicitly disables transaction splitting. There is no change to production wallet code, no security fix, and no indication of a vulnerability.

This commit fixes a bug where the wallet RPC component treated the same proxy address as different if one version included a scheme prefix like 'socks5://' and the other did not. Previously, this caused an unnecessary error when setting a daemon connection. The fix normalizes proxy URIs before comparing them, so equivalent addresses are recognized as the same. It is a usability and correctness fix rather than a clear-cut security vulnerability.

This is a tiny one-line change in a Java library that talks to the Monero cryptocurrency wallet. The library now explicitly ignores a new 'sources' field returned by the Monero wallet RPC when parsing transfer data. It prevents the parser from falling through to an 'unknown field' error or warning, but does not by itself fix a security vulnerability. It is best characterized as a compatibility/robustness update.

This commit adds a new helper method to check whether a web address points to the same computer (a 'loopback' address like 127.0.0.1 or localhost). It is purely a utility addition with tests and does not change any existing behavior or fix a known bug on its own.

This commit only updates generated Java API documentation files (javadocs). It adds an index entry and search index entry for a new utility method, isLoopbackUrl(), in the NetworkUtils class. There are no source code changes, no functional changes, and no security fixes or security-relevant behavior changes in this commit.

This commit only regenerates the project's Javadoc HTML documentation. It does not change any source code, build scripts, or runtime behavior. The documentation now reflects a new NetworkUtils helper class and marks an older MoneroUtils.parseUri method as deprecated, but these are already-existing code facts being documented, not new code changes.

This commit adds an optional switch that lets users turn off HTTPS/TLS certificate verification when the Java library connects to a Monero daemon or wallet RPC server. By default verification stays ON, so ordinary users are not affected. However, if a developer or user explicitly disables it, an attacker on the same network could intercept the connection with a fake certificate and steal passwords, transaction data, or manipulate RPC commands. The change also fixes IPv6 address handling when connecting through a SOCKS proxy.

This commit only updates generated Javadoc HTML documentation files. It does not change any source code, runtime behavior, or fix any security issue. The visible additions are documentation entries for new method overloads and a new regtest configuration option that already exist in the codebase.

This commit adds support for a 'regtest' (regression test) mode flag when opening or creating full wallets through the Java JNI bridge. Regtest is a private, sandboxed Monero network used for testing, similar to a practice environment. The change also explicitly blocks the regtest option for RPC wallets, where it is not supported. There is no direct security vulnerability in the diff itself; it is a feature addition for testing configuration. The main security consideration is that if a user mistakenly enables regtest on a mainnet wallet, it could cause confusion or incorrect behavior, but the code enforces that regtest can only be used with mainnet network type.

This commit removes a loop in a test that repeatedly changed a wallet password. The change is purely a test-code simplification and does not alter any production wallet logic. It is not a security fix.

This commit adds a new optional flag to the Monero wallet's multisig import function, letting callers choose whether the wallet automatically refreshes after importing multisig data. It is a straightforward API enhancement that preserves the previous default behavior (refresh enabled). There is no indication in the commit that this fixes a security bug or vulnerability.

This is a one-line bug fix for a NullPointerException (NPE) in the Java Monero wallet library. Before the fix, the code tried to read a proxy setting from a connection object without first checking whether the connection object existed. If no daemon connection was provided, the program would crash. The fix adds a simple null check. It is a defensive coding fix, not an obvious security vulnerability, though unhandled crashes can sometimes be abused to deny service or mask other behavior.

This commit only adds comments (TODOs) to two test methods and changes one test to repeat 15 times instead of once. It documents that two tests sometimes crash on Apple Silicon Macs but work on Intel, possibly due to JNI binaries. There is no code fix or security change.

This commit only updates the package version number from 0.8.42 to 0.8.43 in three files: the README, the Maven build file, and a Java source file that reports the library version. There are no code behavior changes, no bug fixes, and no security-related modifications.

This is a one-line bug fix in a Java library that talks to the Monero cryptocurrency wallet. The developer added a missing setting that marks confirmed transactions as no longer being in the memory pool (the waiting area for unconfirmed transactions). Without this setting, filters that ask 'show me only transactions still in the pool' could include already-confirmed transactions by mistake, leading to confusing or incorrect wallet data. There is no direct security attack shown in the commit itself.

This is a small test-only change. The developer fixed three test methods so they correctly configure whether a transaction should be relayed immediately or created first and relayed separately. No production wallet code was changed, and there is no security issue here.

This commit adds a check that prevents the wallet from later changing the proxy settings it was started with. If the wallet was launched with a proxy, any later attempt to set a different proxy (or no proxy) now throws an error instead of silently switching. This is a defensive hardening change that reduces the chance of traffic accidentally bypassing the intended proxy.

This commit only updates the library's version number from 0.8.41 to 0.8.42 in three places: the README, the Maven build file, and a Java source file that returns the version string. There are no code behavior changes, no bug fixes, and no security-related modifications.

This commit is a routine version bump from 0.8.40 to 0.8.41. It only updates version strings in the README, Maven project file, and a Java source file. There are no code logic changes, bug fixes, or security-related modifications.