monzero-core.git/contrib/epee/include/net/connection_basic.hpp, branch v0.15.0.1Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.15.0.12019-07-17T14:22:37ZAdded support for "noise" over I1P/Tor to mask Tx transmission.2019-07-17T14:22:37ZLee Clagettcode@leeclagett.com2019-05-16T20:34:22Zurn:sha1:3b24b1d082da28da15dc5e3aeaa0ebebe7758f2fAdd ref-counted buffer byte_slice. Currently used for sending TCP data.2019-07-16T16:30:35ZLee Clagettcode@leeclagett.com2019-05-11T15:38:35Zurn:sha1:bdfc63ae4ddc52e2dece2a031a91509418206cb0remove obsolete save_graph skeleton code2019-05-10T14:17:18Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2019-05-09T17:16:26Zurn:sha1:6abaaaa994c79cbeea37f6b0079ca6b24ecef3a5Pass SSL arguments via one class and use shared_ptr instead of reference2019-04-07T04:44:37ZLee Clagettcode@leeclagett.com2019-03-15T04:03:32Zurn:sha1:21eb1b0725717ad013d3e2b00fbfc3b84ad04699Update 2019 copyright2019-03-05T21:05:34ZbinaryFatebinaryfate@users.noreply.github.com2019-03-05T21:05:34Zurn:sha1:1f2930ce0bec07e28958c059444151ad4968e1e6epee: add SSL support2019-02-02T20:05:33Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-06-14T22:44:48Zurn:sha1:24569454086a366e0bd0cd9b33b0b34661fe7af8
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.
Adding initial support for broadcasting transactions over Tor2019-01-28T23:56:33ZLee Clagettcode@leeclagett.com2018-12-16T17:57:44Zurn:sha1:973403bc9f54ab0722b67a3c76ab6e7bafbfeedc
- 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).
Removed a lot of unnecessary includes2018-11-15T16:29:34ZMartijn Ottogit@martijnotto.nl2018-11-15T16:29:34Zurn:sha1:bd98e99c8095cf05c4d3282c888a87745ad1c559connection_basic: remove unused floating time start time2018-10-02T17:28:46Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-10-02T09:54:38Zurn:sha1:758d7684863b8ff001758c4360ed7087245eac03Update 2018 copyright2018-01-26T15:03:20Zxmr-ericeric@moneroeric.com2018-01-07T05:05:16Zurn:sha1:18216f19dd479466cb7fd38f52d23bddfcfd4880