Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2019-02-02 | epee: add SSL support | moneromooo-monero | 1 | -1/+1 | |
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-01-22 | add a bulletproof version, new bulletproof type, and rct config | moneromooo-monero | 1 | -1/+1 | |
This makes it easier to modify the bulletproof format | |||||
2018-12-18 | device/trezor: store tx_prefix_hash in tx key aux | Dusan Klinec | 1 | -0/+3 | |
- tx_prefix_hash is required in the key derivation for decryption of the tx keys | |||||
2018-12-04 | device/trezor: device/trezor: correct device initialization, status check | Dusan Klinec | 1 | -1/+1 | |
- checks if the device is in the correct usable state - implements check for the v2.0.9 firmware which does not support payment IDs - simple transacttion check, payment id fmt consistency - minor fixes, refactoring, webusb session counting fix | |||||
2018-12-04 | device/trezor: python2 compatibility - bundle dependencies | Dusan Klinec | 5 | -8/+248 | |
2018-11-25 | device/trezor: webusb transport added, cmake fixes | Dusan Klinec | 5 | -40/+555 | |
- webusb transport based on libusb added. Provides direct access to Trezor via USB, no need for Trezor bridge. - trezor protocol message handler improved, no recursion used. Ready for upcoming integration tests. - libusb (for docker) bumped from v1.0.9 to v1.0.22, newer version required for webusb transport, for device enumeration. - cmake improvements and fixes. Cmake Trezor checks are moved to a dedicated CheckTrezor.cmake file. In case of a problem Trezor is excluded from build. - ifdefs made consistent to Ledger. - UDP Transport enumeration disabled by default in release mode | |||||
2018-11-02 | device/trezor: trezor support added | Dusan Klinec | 12 | -0/+2895 | |