| Commit message (Collapse) | Author | Age | Files | Lines |
| |\
| |
| |
| | |
8655ba04 wallet_rpc_server: adjust small ring sizes to 5 for v6 (moneromooo-monero)
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
359517c7 wallet_rpc_server: fix possible privacy leak in on_import_key_images() (Jaquee)
20495b27 simplewallet: fix possible privacy leak in import_key_images() (Jaquee)
|
| | |/ |
|
| |\ \
| |/
|/|
| | |
c97d1bd3 wallet: return unlock_time in get_transfers (moneromooo-monero)
|
| | |
| |
| |
| | |
also show it in simplewallet's show_transfer
|
| | | |
|
| |\ \
| | |
| | |
| | | |
cb0b5594 Move OpenAlias console input back from libs (moneromooo-monero)
|
| | |/
| |
| |
| |
| |
| |
| | |
Library code should definitely not ask for console input unless
it's clearly an input function. Delegating the user interaction
part to the caller means it can now be used by a GUI, or have a
decision algorithm better adapted to a particular caller.
|
| |/
|
|
|
| |
also add do_not_relay flag to them, so it now becomes possible
to create a tx without sending it yet
|
| |\
| |
| |
| | |
f98bf48b Minor cleanup: tab vs. space + logs messages (binaryFate)
|
| | | |
|
| |\ \
| | |
| | |
| | | |
5a09d79c Fix #2120: return per-tx amount in transfer_split RPC call. (binaryFate)
|
| | |/ |
|
| |/ |
|
| |
|
|
|
|
|
| |
It sweeps all outputs below the given threshold
This is available via the existing sweep_all RPC, by setting
amount_threshold the desired amount (in atomic units)
|
| |
|
|
|
| |
Reviewed and squashed. Open/Create is only allowed if no walletfile
was specified at startup.
|
| | |
|
| | |
|
| |\
| |
| |
| | |
e9175cec wallet_rpc_server: make a few RPCs unavailable in restricted mode (moneromooo-monero)
|
| | |
| |
| |
| | |
Address book modification, setting tx nodes, importing key images
|
| |\ \
| | |
| | |
| | | |
d0238313 use const references in catch blocks (moneromooo-monero)
|
| | |/ |
|
| |\ \
| | |
| | |
| | |
| | | |
3fa59755 wallet2: call is_key_image_spent in blocks in rescan_spent (moneromooo-monero)
9d134e86 wallet_rpc_server: add a rescan_spent RPC (moneromooo-monero)
|
| | |/ |
|
| |/ |
|
| | |
|
| |
|
|
|
| |
and remove trusted_daemon fields from transfer RPCs,
it is much friendlier on users
|
| | |
|
| | |
|
| |\
| |
| |
| | |
ce7fcbb4 Add server auth to monerod, and client auth to wallet-cli and wallet-rpc (Lee Clagett)
|
| | | |
|
| |/ |
|
| | |
|
| |\
| |
| |
| | |
69d2ad39 wallet_rpc_server: fix logs going to the wrong file (moneromooo-monero)
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
| |
This avoids indirectly leaking the real output to the daemon,
and is faster.
This will still happen for more complex cases, especially
when cancelling a tx and "re-rolling" it.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This replaces the epee and data_loggers logging systems with
a single one, and also adds filename:line and explicit severity
levels. Categories may be defined, and logging severity set
by category (or set of categories). epee style 0-4 log level
maps to a sensible severity configuration. Log files now also
rotate when reaching 100 MB.
To select which logs to output, use the MONERO_LOGS environment
variable, with a comma separated list of categories (globs are
supported), with their requested severity level after a colon.
If a log matches more than one such setting, the last one in
the configuration string applies. A few examples:
This one is (mostly) silent, only outputting fatal errors:
MONERO_LOGS=*:FATAL
This one is very verbose:
MONERO_LOGS=*:TRACE
This one is totally silent (logwise):
MONERO_LOGS=""
This one outputs all errors and warnings, except for the
"verify" category, which prints just fatal errors (the verify
category is used for logs about incoming transactions and
blocks, and it is expected that some/many will fail to verify,
hence we don't want the spam):
MONERO_LOGS=*:WARNING,verify:FATAL
Log levels are, in decreasing order of priority:
FATAL, ERROR, WARNING, INFO, DEBUG, TRACE
Subcategories may be added using prefixes and globs. This
example will output net.p2p logs at the TRACE level, but all
other net* logs only at INFO:
MONERO_LOGS=*:ERROR,net*:INFO,net.p2p:TRACE
Logs which are intended for the user (which Monero was using
a lot through epee, but really isn't a nice way to go things)
should use the "global" category. There are a few helper macros
for using this category, eg: MGINFO("this shows up by default")
or MGINFO_RED("this is red"), to try to keep a similar look
and feel for now.
Existing epee log macros still exist, and map to the new log
levels, but since they're used as a "user facing" UI element
as much as a logging system, they often don't map well to log
severities (ie, a log level 0 log may be an error, or may be
something we want the user to see, such as an important info).
In those cases, I tried to use the new macros. In other cases,
I left the existing macros in. When modifying logs, it is
probably best to switch to the new macros with explicit levels.
The --log-level options and set_log commands now also accept
category settings, in addition to the epee style log levels.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| | |
f4772bae Fix a few minor typos (Pierre Boyer)
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This is intended to catch traffic coming from a web browser,
so we avoid issues with a web page sending a transfer RPC to
the wallet. Requiring a particular user agent can act as a
simple password scheme, while we wait for 0MQ and proper
authentication to be merged.
|