| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2023-01-16 | Copyright: Update to 2023 | mj-xmr | 1 | -1/+1 | |
| Co-authored-by: plowsof <plowsof@protonmail.com> extra files | |||||
| 2022-03-04 | Copyright: Update to 2022 | mj-xmr | 1 | -1/+1 | |
| 2021-10-10 | download: fix leak | moneromooo-monero | 1 | -1/+9 | |
| A shared_ptr as by value capture will keep the object alive | |||||
| 2020-05-06 | Update copyright year to 2020 | SomaticFanatic | 1 | -1/+1 | |
| Update copyright year to 2020 | |||||
| 2019-11-26 | download: catch exceptions checking for size | moneromooo-monero | 1 | -5/+9 | |
| Happens on at least one windows box | |||||
| 2019-03-05 | Update 2019 copyright | binaryFate | 1 | -1/+1 | |
| 2019-02-02 | epee: add SSL support | moneromooo-monero | 1 | -2/+2 | |
| 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-11-15 | Removed a lot of unnecessary includes | Martijn Otto | 1 | -3/+0 | |
| 2018-01-26 | Readd copyright starting date | xmr-eric | 1 | -1/+1 | |
| 2018-01-26 | Update 2018 copyright | xmr-eric | 1 | -1/+1 | |
| 2017-12-25 | Merge pull request #2929 | Riccardo Spagni | 1 | -7/+49 | |
| ae55bacd resumption support for updates using range requests (moneromooo-monero) fe0fae50 epee: add a get_file_size function (moneromooo-monero) | |||||
| 2017-12-15 | resumption support for updates using range requests | moneromooo-monero | 1 | -7/+49 | |
| 2017-12-14 | download: SSL suport | moneromooo-monero | 1 | -2/+3 | |
| 2017-03-05 | download: check available disk space before downloading | moneromooo-monero | 1 | -0/+8 | |
| We don't check *while* the download happens, so it might still be that we don't have enough space later | |||||
| 2017-03-05 | download: give download threads distinct names | moneromooo-monero | 1 | -0/+5 | |
| 2017-03-05 | download: async API | moneromooo-monero | 1 | -25/+144 | |
| 2017-02-20 | core: updates can now be downloaded (and SHA256 hash checked) | moneromooo-monero | 1 | -0/+138 | |
 |
index : monero.git | |
| Monero: the secure, private, untraceable cryptocurrency |
| aboutsummaryrefslogtreecommitdiff |