aboutsummaryrefslogtreecommitdiff
path: root/contrib/epee/src/connection_basic.cpp (unfollow)
AgeCommit message (Collapse)AuthorFilesLines
2022-04-18Trimming FatJeffrey1-1/+0
Remove unused include statements or unused definitions.
2022-03-04Copyright: Update to 2022mj-xmr1-1/+1
2020-05-06Update copyright year to 2020SomaticFanatic1-1/+1
Update copyright year to 2020
2019-09-06epee: connection_basic: resolve CID 203916 (UNINIT_CTOR)anonimal1-0/+1
2019-09-06epee: connection_basic: resolve CID 203920 (UNINIT_CTOR)anonimal1-0/+1
2019-07-17Added support for "noise" over I1P/Tor to mask Tx transmission.Lee Clagett1-2/+2
2019-05-10remove obsolete save_graph skeleton codemoneromooo-monero1-3/+0
2019-04-07Pass SSL arguments via one class and use shared_ptr instead of referenceLee Clagett1-20/+27
2019-03-21epee: fix build with boost 1.70.0moneromooo-monero1-2/+8
get_io_service was deprecated, and got removed
2019-03-08connection_basic: remove debug exception ^_^moneromooo-monero1-1/+0
2019-03-05Update 2019 copyrightbinaryFate1-1/+1
2019-02-02epee: add SSL supportmoneromooo-monero1-9/+37
RPC connections now have optional tranparent SSL. An optional private key and certificate file can be passed, using the --{rpc,daemon}-ssl-private-key and --{rpc,daemon}-ssl-certificate options. Those have as argument a path to a PEM format private private key and certificate, respectively. If not given, a temporary self signed certificate will be used. SSL can be enabled or disabled using --{rpc}-ssl, which accepts autodetect (default), disabled or enabled. Access can be restricted to particular certificates using the --rpc-ssl-allowed-certificates, which takes a list of paths to PEM encoded certificates. This can allow a wallet to connect to only the daemon they think they're connected to, by forcing SSL and listing the paths to the known good certificates. To generate long term certificates: openssl genrsa -out /tmp/KEY 4096 openssl req -new -key /tmp/KEY -out /tmp/REQ openssl x509 -req -days 999999 -sha256 -in /tmp/REQ -signkey /tmp/KEY -out /tmp/CERT /tmp/KEY is the private key, and /tmp/CERT is the certificate, both in PEM format. /tmp/REQ can be removed. Adjust the last command to set expiration date, etc, as needed. It doesn't make a whole lot of sense for monero anyway, since most servers will run with one time temporary self signed certificates anyway. SSL support is transparent, so all communication is done on the existing ports, with SSL autodetection. This means you can start using an SSL daemon now, but you should not enforce SSL yet or nothing will talk to you.
2019-01-28Adding initial support for broadcasting transactions over TorLee Clagett1-12/+16
- 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-15Removed a lot of unnecessary includesMartijn Otto1-33/+0
2018-10-02connection_basic: remove unused floating time start timemoneromooo-monero1-7/+0
2018-01-26Update 2018 copyrightxmr-eric1-1/+1
2018-01-10epee: remove dependency on commonmoneromooo-monero1-1/+0
2017-12-16move connection_basic and network_throttle from src/p2p to epeemoneromooo-monero1-2/+2
These even had the epee namespace. This fixes some ugly circular dependencies.
2017-11-28Corrections in rate limiting / trottle code, especially in 'out' directionrbrunner71-9/+4
Deleted 3 out of 4 calls to method connection_basic::sleep_before_packet that were erroneous / superfluous, which enabled the elimination of a "fudge" factor of 2.1 in connection_basic::set_rate_up_limit; also ended the multiplying of limit values and numbers of bytes transferred by 1024 before handing them over to the global throttle objects
2017-11-14remove "using namespace std" from headersmoneromooo-monero1-2/+2
It's nasty, and actually breaks on Solaris, where if.h fails to build due to: struct map *if_memmap;
2017-08-10p2p: get net log spam down a bitmoneromooo-monero1-4/+3
2017-07-31some include cleanupmoneromooo-monero1-5/+5
2017-02-21update copyright year, fix occasional lack of newline at line endRiccardo Spagni1-1/+1
2017-01-22Remove boost/foreach.cpp includesMiguel Herranz1-1/+0
2017-01-16Change logging to easylogging++moneromooo-monero1-26/+6
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-05-18src: p2p: add exception spec to throwing destructorsredfish1-1/+1
The destructors get a noexcept(true) spec by default, but these destructors in fact throw exceptions. An alternative fix might be to not throw (most if not all of these throws are non-essential error-reporting/logging).
2016-03-28connection_basic: avoid gratuitous exceptionmoneromooo-monero1-2/+2
The remote endpoint is usually invalid, so use a version of the call that returns an error code instead.
2015-12-31updated copyright yearRiccardo Spagni1-1/+1
2015-06-06properly decrement p2p socket countThomas Winget1-0/+1
2015-05-31cleaning up, removing redundant files, renaming, fixing incorrect licensesRiccardo Spagni1-1/+1
2015-05-17s/terget/target/moneromooo-monero1-4/+4
2015-05-17print limits when running limit commands with no argumentsmoneromooo-monero1-0/+17
It's more user friendly that an error message saying the command does not exist.
2015-04-08[fix] Network 1.8: unlimited the RPC connectionsrfree2monero1-0/+12
works for unit tests build, too
2015-02-242014 network limit 1.3 fix log/path/data +utilsrfree2monero1-0/+1
+toc -doc -drmonero Fixed the windows path, and improved logging and data (for graph) logging, fixed some locks and added more checks. Still there is a locking error, not added by my patches, but present in master version (locking of map/list of peers).
2015-02-202014 network limit 1.2 +utils +toc -doc -drmonerorfree2monero1-12/+3
new update of the pr with network limits more debug options: discarding downloaded blocks all or after given height. trying to trigger the locking errors. debug levels polished/tuned to sane values. debug/logging improved. warning: this pr should be correct code, but it could make an existing (in master version) locking error appear more often. it's a race on the list (map) of peers, e.g. between closing/deleting them versus working on them in net-limit sleep in sending chunk. the bug is not in this code/this pr, but in the master version. the locking problem of master will be fixed in other pr. problem is ub, and in practice is seems to usually cause program abort (tested on debian stable with updated gcc). see --help for option to add sleep to trigger the error faster.
2015-02-202014 network limit 1.1 +utils +toc -doc -drmonerorfree2monero1-117/+50
Update of the PR with network limits works very well for all speeds (but remember that low download speed can stop upload because we then slow down downloading of blockchain requests too) more debug options fixed pedantic warnings in our code should work again on Mac OS X and FreeBSD fixed warning about size_t tested on Debian, Ubuntu, Windows(testing now) TCP options and ToS (QoS) flag FIXED peer number limit FIXED some spikes in ingress/download FIXED problems when other up and down limit
2015-02-202014 network limit 1.0a +utils +toc -doc -drmonerorfree2monero1-0/+362
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)
generated by cgit v1.2.3 (git 2.25.1) at 2025-02-02 02:01:22 +0000