monero.git - Monero: the secure, private, untraceable cryptocurrency

Age	Commit message (Collapse)	Author	Files	Lines
2020-07-20	wallet2_api: implement runtime proxy configuration	xiphon	1	-2/+2

2019-10-25	net: link with libzmq	moneromooo-monero	1	-1/+1

2019-07-22	Dropping cppzmq dependency; adding some zmq utils	Lee Clagett	1	-2/+4

2019-07-17	Added support for "noise" over I1P/Tor to mask Tx transmission.	Lee Clagett	1	-2/+2

2019-03-25	Added socks proxy (tor/i2pd/kovri) support to wallet	Lee Clagett	1	-2/+2

2019-03-05	device/trezor: debugging features, trezor tests	Dusan Klinec	1	-1/+1

2019-02-13	debug compilation fix: net lib missing common deps	Dusan Klinec	1	-1/+1
	``` Undefined symbols for architecture x86_64: "common_category()", referenced from: make_error_code(common_error) in parse.cpp.o make_error_code(common_error) in tor_address.cpp.o "boost::system::detail::system_category_ncx()", referenced from: boost::system::system_category() in parse.cpp.o boost::system::system_category() in socks.cpp.o boost::system::system_category() in libepee.a(net_utils_base.cpp.o) "boost::system::detail::generic_category_ncx()", referenced from: boost::system::generic_category() in parse.cpp.o boost::system::generic_category() in socks.cpp.o boost::system::generic_category() in tor_address.cpp.o boost::system::generic_category() in libepee.a(string_tools.cpp.o) boost::system::generic_category() in libepee.a(net_utils_base.cpp.o) ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[3]: * [src/net/libnet.dylib] Error 1 make[2]: * [src/net/CMakeFiles/net.dir/all] Error 2 ```
2019-01-30	i2p: initial support	Jethro Grassie	1	-2/+2

2019-01-28	Adding initial support for broadcasting transactions over Tor	Lee Clagett	1	-8/+12
	- Support for ".onion" in --add-exclusive-node and --add-peer - Add --anonymizing-proxy for outbound Tor connections - Add --anonymous-inbounds for inbound Tor connections - Support for sharing ".onion" addresses over Tor connections - Support for broadcasting transactions received over RPC exclusively over Tor (else broadcast over public IP when Tor not enabled).
2018-11-17	Remove -Werror	moneromooo-monero	1	-5/+0
	It is an annoying piece of garbage
2018-01-26	Update 2018 copyright	xmr-eric	1	-1/+1

2017-10-08	cmake: build tests last	redfish	1	-0/+5
	Keep -Werror for src, contrib and do not pass it for tests/
2017-02-21	update copyright year, fix occasional lack of newline at line end	Riccardo Spagni	1	-1/+1

2017-01-16	Change logging to easylogging++	moneromooo-monero	1	-1/+0
	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.
2016-12-13	Adding HTTP Digest Auth (but not yet enabled)	Lee Clagett	1	-0/+1

2015-12-31	updated copyright year	Riccardo Spagni	1	-1/+1

2015-05-31	cleaning up, removing redundant files, renaming, fixing incorrect licenses	Riccardo Spagni	1	-0/+27

2015-02-20	2014 network limit 1.0a +utils +toc -doc -drmonero	rfree2monero	1	-0/+3
	commands and options for network limiting works very well e.g. for 50 KiB/sec up and down ToS (QoS) flag peer number limit TODO some spikes in ingress/download TODO problems when other up and down limit added "otshell utils" - simple logging (with colors, text files channels)