monzero-core.git/contrib/epee/include/net, branch v0.10.0Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.10.02016-09-18T19:32:02Zepee: optionally restrict HTTP service to a configurable user agent2016-09-18T19:32:02Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-09-07T20:38:41Zurn:sha1:eeb2bbc0fcc9c5afa2c3aa12915b4d3f31115e56
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.
epee: do not try network resolution if loopback worked2016-09-01T17:12:39Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-09-01T17:12:39Zurn:sha1:0d7ce00793a5e6b9f20f7e6f09313f0240800674
Fixes the wallet being unable to connect to the daemon
when there is no NIC.
contrib: epee: add missing noexcept spec to class decl2016-06-22T13:05:53Zredfishredfish@galactica.pw2016-06-21T23:36:26Zurn:sha1:72287d121a5efbb455566d56612daab571a0141b
The noexcept specs were added to make GCC 6.1.1 happy (#846), but this
one was missing (because GCC did not complain about it on Linux, but
does complain on OSX).
contrib: epee: add exception spec to throwing destructors2016-05-18T05:02:27Zredfishredfish@galactica.pw2016-05-18T04:59:07Zurn:sha1:c2d7300d2ebea0c5567268f320fe3427f4399667
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).
Don't allow 'flush_txpool' and 'setbans' JSON_RPC methods when running in restricted mode.2016-05-14T06:06:04Zosenseiadmin@monerohash.com2016-05-14T06:06:04Zurn:sha1:9f8bc4946b3993ad4437936dcae705d2c8f1116aabstract_tcp_server2: fix send queue limit warning spam2016-04-17T10:47:22Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-04-17T10:47:22Zurn:sha1:3102feb56c2274313e40d1d13cb2761f7796bb9b
When the send queue limit is reached, it is likely to not drain
any time soon. If we call close on the connection, it will stay
alive, waiting for the queue to drain before actually closing,
and will hit that check again and again. Since the queue size
limit is the reason we're closing in the first place, we call
shutdown directly.
abstract_tcp_server2: avoid deadlock waiting for send queue to drain2016-04-17T10:45:38Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-04-17T10:45:38Zurn:sha1:6bca9a8ef435b6b8a5dca917ec848c076c3a971e
If we reach the send queue size limit, we need to release the lock,
or we will deadlock and it will never drain.
If we reach that limit, it's likely there's another problem in the
first place though, so it will probably not drain in practice either,
unless some kind of transient network timeout.
abstract_tcp_server2: possible fix for exception in handle_accept2016-03-27T11:53:20Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-03-27T11:53:20Zurn:sha1:43962f41031d85778e4ae5949ec1a6141a1bcac2Revert "Print stack trace upon exceptions"2016-03-21T10:12:23Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-03-21T10:12:12Zurn:sha1:f7301c3563e7ae19b8d7c65d8bc88f3c42eefc09
Ain't nobody got time for link/cmake skullduggery.
This reverts commit fff238ec94ac6d45fc18c315d7bc590ddfaad63d.
Merge pull request #7362016-03-20T19:28:11ZRiccardo Spagniric@spagni.net2016-03-20T19:28:11Zurn:sha1:f6317ec1c0a9e5644deeea07ee8c392585e39584
2b4cab3 epee: fix potential hang on exit (moneromooo-monero)