Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.15.0.5 2019-04-15T09:14:12Z 2019-04-15T09:14:12Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-04-13T09:19:38Z urn:sha1:b18f0b10513b0455723518a634595b2f36d5ea25 It will avoid connecting to a daemon (so useful for cold signing using a RPC wallet), and not perform DNS queries. 2019-04-11T10:46:41Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2019-03-29T22:03:52Z urn:sha1:9f8dc4ce515f52ebb2a434ba6d1d9f47bfeac612 displays total sent and received bytes 2019-04-07T04:44:37Z Lee Clagett code@leeclagett.com 2019-03-15T04:03:32Z urn:sha1:21eb1b0725717ad013d3e2b00fbfc3b84ad04699 2019-04-07T03:47:06Z Lee Clagett code@leeclagett.com 2019-03-12T02:01:03Z urn:sha1:a3b0284837c9ea10865e6ddeb7f1244d621ae5c0 Specifying SSL certificates for peer verification does an exact match, making it a not-so-obvious alias for the fingerprints option. This changes the checks to OpenSSL which loads concatenated certificate(s) from a single file and does a certificate-authority (chain of trust) check instead. There is no drop in security - a compromised exact match fingerprint has the same worse case failure. There is increased security in allowing separate long-term CA key and short-term SSL server keys. This also removes loading of the system-default CA files if a custom CA file or certificate fingerprint is specified. 2019-04-06T14:00:18Z Riccardo Spagni ric@spagni.net 2019-04-06T14:00:18Z urn:sha1:38317f384c912cd1a34f78f20008ec27f39ad0ae 59776a64 epee: some more minor JSON parsing speedup (moneromooo-monero) 2019-03-25T14:29:29Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-12-27T19:15:05Z urn:sha1:59776a64ffad2523be7789d1d034031f7ee59a58 2019-03-25T01:35:13Z Lee Clagett code@leeclagett.com 2019-01-23T21:37:43Z urn:sha1:7acfa9f3cc7b52c0f4776dde3c3f80674cc3306f 2019-03-05T13:16:08Z Martijn Otto git@martijnotto.nl 2018-06-14T22:44:48Z urn:sha1:057c279cb4d5c16990570d281bd1bc568796cbb2 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-02-02T20:05:33Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2018-06-14T22:44:48Z urn: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. 2018-03-15T16:25:38Z Dimitris Apostolou dimitris.apostolou@icloud.com 2018-03-01T11:36:19Z urn:sha1:57c0b1ed9f15ca27892a8737156c3b8e32a1625e