monzero-core.git/contrib/epee/include/net, branch v0.9.0Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.9.02015-12-23T11:19:16Zepee: regularly cleanup connections we kept a reference to2015-12-23T11:19:16Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-23T11:19:16Zurn:sha1:22581a04415c571461368c434ece72e5756d4fbd
Since connections from the ::connect method are now kept in
a deque to be able to cancel them on exit, this leaks both
memory and a file descriptor. Here, we clean those up after
30 seconds, to avoid this. 30 seconds is higher then the
5 second timeout used in the async code, so this should be
safe. However, this is an assumption which would break if
that async code was to start relying on longer timeouts.
epee: fix hang on exit2015-12-22T12:39:02Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-22T12:31:22Zurn:sha1:1e2f2d7da0ee22e35670856ad964671848e186b4
When the boost ioservice is stopped, pending work notifications
will not happen. This includes deadline timers, which would
otherwise time out the now cancelled I/O operations. When this
happens just after starting a new connect operation, this can
leave that operations in a state where it won't receive either
the completion notification nor a timeout, causing a hang.
This is fixed by keeping a list of connections corresponding
to the connect operations, and cancelling them before stopping
the boost ioservice.
Note that the list of these connections can grow unbounded, as
they're never cleaned up. Cleaning them up would involve
working out which connections do not have any pending work,
and it's not quite clear yet how to go about this.
core_rpc_server: add a --restricted-rpc option2015-11-27T18:27:24Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-11-27T18:24:29Zurn:sha1:75742977a8cd765175c1d3e39e2e74d25c6ca774
It does not expose the RPC for commands like start_mining, etc
(ie, commands a public node operator might want to be restricted)
Add IP blocking for misbehaving nodes (adapted from Boolberry)2015-11-23T18:06:20ZJavier Smoothiamjaviersmooth@gmail.com2015-11-23T17:34:55Zurn:sha1:4cea2b13b221bed66023254dd3356f2548a08df4
With minor cleanup and fixes (spelling, indent) by moneromooo
[fix] log level change. compilation: dns, tests2015-04-10T14:54:21Zrfree2monerorfreemonero@op.pl2015-04-10T14:13:57Zurn:sha1:32c19c6c3d677564d217ba31c16fdfc84b4faf80
old unbound #warning does not block compilation
unit tests build fine. Even though the RPC/P2P network type is required again
[fix] Network 1.8: unlimited the RPC connections2015-04-08T17:54:07Zrfree2monerorfreemonero@op.pl2015-04-08T17:54:07Zurn:sha1:9bfa593eee5a528c70dfaed39feb140a7b10e8b5
works for unit tests build, too
[fix] mac os x includes std::random...2015-04-01T18:25:53Zrfree2monerorfreemonero@op.pl2015-04-01T18:25:53Zurn:sha1:44f423477a6ce0971ced31afee38e259b2b571d6remerged; commands JSON. logging upgrade. doxygen2015-04-01T17:00:45Zrfree2monerorfreemonero@op.pl2015-04-01T17:00:45Zurn:sha1:c511abf0058b8c1d020255faaad418b0ffd2eb26Merge remote-tracking branch 'monero-official/master' into network-1.6-work12015-04-01T16:24:45Zrfree2monerorfreemonero@op.pl2015-04-01T16:24:45Zurn:sha1:3cbdf198f168e113f12fa49d016133c434964ed7Restore daemon interactive mode2015-03-27T12:01:30ZThomas Wingettewinget@gmail.com2015-03-27T12:01:30Zurn:sha1:a0590d29cd9949c65a4cd67630a84410a30d33fe
Daemon interactive mode is now working again.
RPC mapped calls in daemon and wallet have both had connection_context
removed as an argument as that argument was not being used anywhere.