mirror of
https://git.hush.is/hush/hush3.git
synced 2025-07-29 00:03:54 -04:00
Compare commits
3 Commits
172e6f7977
...
4ed576a7e2
Author | SHA1 | Date | |
---|---|---|---|
|
4ed576a7e2 | ||
|
a358acab0b | ||
|
ccc86839b9 |
@ -14,7 +14,24 @@ Equihash (200,9) (ASIC)
|
|||||||
|
|
||||||
## P2P
|
## P2P
|
||||||
|
|
||||||
TLS1.3 via WolfSSL is enforced for all network connections as of v3.6.1
|
TLS1.3 via WolfSSL is enforced for all network connections as of v3.6.1 .
|
||||||
|
Many ciphersuites are technically supported by TLS1.3 but many of them
|
||||||
|
are ancient, proved to be less secure than intended or likely backdoored.
|
||||||
|
Hush only uses what are widely considered to be the most secure and [best ciphersuites](https://ciphersuite.info/cs/).
|
||||||
|
|
||||||
|
New Hush P2P connections randomly choose between these two ciphersuites each
|
||||||
|
time a new connection to a peer is created:
|
||||||
|
|
||||||
|
* `TLS_AES_256_GCM_SHA384`
|
||||||
|
* `TLS_CHACHA20_POLY1305_SHA256`
|
||||||
|
|
||||||
|
Encrypted P2P connections are important because it means passive network spies,
|
||||||
|
such as ISPs, cannot tell what nodes are communicating to each other and also
|
||||||
|
prevents certain attacks against privacy at the network level, such as looking
|
||||||
|
for which node was the first to relay a transaction. Bitcoin has no protection
|
||||||
|
against this which is why it's trivial for network spies to tell which node
|
||||||
|
(and hence which IP address) created a certain transaction and hence which
|
||||||
|
IP address owns which addresses.
|
||||||
|
|
||||||
## RPC
|
## RPC
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user