You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SNI addresses of the format /ip4/192.0.2.0/tcp/1234/tls/sni/foo.example.com/ws don't seem to be supported for websockets in rust-libp2p.
Motivation
autotls is a new service allowing nodes to request a tls certificate matching their peer ID, allowing libp2p nodes to act as wss servers without having to manually configure a certificate tied to a domain name. The default advertised addresses are of the format /ip4/192.0.2.0/tcp/1234/tls/sni/192-0-2-0.<peerid>.libp2p.direct/ws, and rust-libp2p nodes were unable to dial these types of addresses. However, rust-libp2p nodes were able to dial addresses like /dns4/192-0-2-0.<peerid>.libp2p.direct/tcp/1234/tls/ws.
cc: @oblique I believe this change would benefit Lumina. If autotls is deployed in celestia-node, it means that browser nodes would be able to connect to much more nodes in the Celestia network.
Are you planning to do it yourself in a pull request?
No
The text was updated successfully, but these errors were encountered:
Description
SNI addresses of the format
/ip4/192.0.2.0/tcp/1234/tls/sni/foo.example.com/ws
don't seem to be supported for websockets inrust-libp2p
.Motivation
autotls
is a new service allowing nodes to request atls
certificate matching their peer ID, allowing libp2p nodes to act aswss
servers without having to manually configure a certificate tied to a domain name. The default advertised addresses are of the format/ip4/192.0.2.0/tcp/1234/tls/sni/192-0-2-0.<peerid>.libp2p.direct/ws
, andrust-libp2p
nodes were unable to dial these types of addresses. However,rust-libp2p
nodes were able to dial addresses like/dns4/192-0-2-0.<peerid>.libp2p.direct/tcp/1234/tls/ws
.Also libp2p websockets spec specifies that
sni
addresses should be supported.Current Implementation
This new address format was added in the specs 3 months ago, hence this may be the reason why it isn't implemented yet.
Related: #5529 (comment)
cc: @oblique I believe this change would benefit Lumina. If
autotls
is deployed in celestia-node, it means that browser nodes would be able to connect to much more nodes in the Celestia network.Are you planning to do it yourself in a pull request?
No
The text was updated successfully, but these errors were encountered: