13 Commits (ed67e5c001d50a2eea5fa24dfc58eba0921d525b)

Author	SHA1	Message	Date
moneromooo-monero	40ab12a773	epee: remove dependency on common	7 years ago
Tim L	0bf0915446	Fix file permission issue ... This branch fixes a file permission issue introduced by 69c37200aa	7 years ago
Tim L	69c37200aa	RPC Add cross origin resource sharing support	7 years ago
Lee Clagett	ce7fcbb4ae	Add server auth to monerod, and client auth to wallet-cli and wallet-rpc	8 years ago
moneromooo-monero	5833d66f65	Change logging to easylogging++ ... 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.	8 years ago
Lee Clagett	d81cb08704	Added (not yet enabled) HTTP client authentication	8 years ago
Lee Clagett	bdc3d7496f	Adding HTTP Digest Auth (but not yet enabled)	8 years ago
moneromooo-monero	eeb2bbc0fc	epee: optionally restrict HTTP service to a configurable user agent ... 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.	8 years ago
fluffypony	32f9d2b783	move modified epee code to new classes, revert license	10 years ago
fluffypony	6fc995fe5d	License updated to BSD 3-clause	10 years ago
mydesktop	3a3a817678	0.8.8update	10 years ago
Antonio Juarez	8efa1313f3	some fixes	10 years ago
Antonio Juarez	296ae46ed8	moved all stuff to github	10 years ago