aboutsummaryrefslogtreecommitdiff
path: root/INSTALL.md
diff options
context:
space:
mode:
authorJon Atack <jon@atack.com>2024-01-07 15:53:08 -0600
committerJon Atack <jon@atack.com>2024-01-07 16:24:08 -0600
commit9d728916b27e18efc6f8839770ed5ec14789fc08 (patch)
tree431b8b319b0959fcca4e101ecefd4a16922997bc /INSTALL.md
parent82ba0f80a0b56bb160c8be1fddd82dbbc4fb3947 (diff)
net: create I2P sessions with both ECIES-X25519 and ElGamal encryption
A Bitcoin Core node may only connect to a peer destination via I2P if both sides have sessions with the same encryption type. The encryption type is a property of the session, not the destination. Sessions may support multiple encryption types. As Bitcoin Core is not currently setting the I2P encryption type when creating sessions, it is using the older default, ElGamal (type 0). This pull updates Bitcoin Core to use both ECIES-X25519 and ElGamal (types 4 and 0, respectively). This allows to connect to I2P peers with either type, and the newer, faster ECIES-X25519 will be preferred. See also the recently updated section "Signature and Encryption Types" in https://geti2p.net/en/docs/api/samv3 Thanks and credit to zzzi2p (https://github.com/zzzi2p) for reporting. Closes https://github.com/bitcoin/bitcoin/issues/29197.
Diffstat (limited to 'INSTALL.md')
0 files changed, 0 insertions, 0 deletions