| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
It was not filled out for in and pool types
|
| |\ \ \
| | | |
| | | |
| | | | |
a2561653 wallet: new option to start background mining (moneromooo-monero)
|
| | |/ /
| | |
| | |
| | |
| | |
| | | |
The setup-background-mining option can be used to select
background mining when a wallet loads. The user will be asked
the first time the wallet is created.
|
| | | |
| | |
| | |
| | |
| | | |
If `--daemon-ssl enabled` is set in the wallet, then a user certificate,
fingerprint, or onion/i2p address must be provided.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Currently if a user specifies a ca file or fingerprint to verify peer,
the default behavior is SSL autodetect which allows for mitm downgrade
attacks. It should be investigated whether a manual override should be
allowed - the configuration is likely always invalid.
|
| | |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |\ \
| | |
| | |
| | | |
678262ab wallet_rpc_server: allow english/local language names in create_wallet (moneromooo-monero)
|
| | | |
| | |
| | |
| | | |
and return both in get_languages
|
| |\ \ \
| | | |
| | | |
| | | | |
16eda54b wallet: use original user address if we have a short payment id (moneromooo-monero)
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
It was not filled out for in and pool types
|
| | |_|/
|/| | |
|
| |\ \ \
| | | |
| | | |
| | | | |
023f2c77 wallet_rpc_server: remove mixin from transfer RPCs (moneromooo-monero)
|
| | |/ /
| | |
| | |
| | | |
it's been a while, only use ring_size now
|
| |\ \ \
| | | |
| | | |
| | | | |
23fb056a wallet_rpc_server: new auto_refresh RPC (moneromooo-monero)
|
| | | | |
| | | |
| | | |
| | | | |
It can enable/disable auto refresh, and set auto refresh period
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
4ee15655 wallet_rpc_server: fix buffer read overflow in string assignment (moneromooo-monero)
|
| | | | | | |
|
| |\ \ \ \ \
| |_|_|_|/
|/| | | |
| | | | | |
a8b98a0b wallet: fix memory only wallets (moneromooo-monero)
|
| | | | | |
| | | | |
| | | | |
| | | | | |
at least when using restore_deterministic_wallet
|
| |\ \ \ \ \
| |_|_|_|/
|/| | | |
| | | | | |
f962449d wallet_rpc_server: include out subaddress indices in get_transfers (moneromooo-monero)
|
| | | |/ /
| |/| | |
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | | |
8b514645 add multisig tx sets to describe_transfer rpc endpoint (spoke0)
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
36451697 Simplify RPC endpoint, emoving second RPC endpoint generate_from_view_key (Joel)
c17c8188 Remove code duplication (Joel)
acb14c10 Add generate_from_view_key RPC method (Joel)
7dd7a3b7 Add generate_from_keys RPC method (Joel)
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | |/ / / |
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | | |
1f2930ce Update 2019 copyright (binaryFate)
|
| | | |/
| |/| |
|
| |/ / |
|
| |\ \
| | |
| | |
| | | |
057c279c epee: add SSL support (Martijn Otto)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| |/ / |
|
| | | |
|
| |\ \
| | |
| | |
| | | |
3d2772a0 wallet-rpc: get balance for all accounts and subaddresses (stoffu)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
8a1ff079 wallet-rpc: get transfers for all accounts and subaddresses (Jethro Grassie)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
5c81a9f1 wallet_rpc_server: add a validate_address RPC (moneromooo-monero)
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
24569454 epee: add SSL support (moneromooo-monero)
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |/ |
|