-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The section about secio is obsolete #91
Comments
At this point transport key are maybe more @infinity0 now than me, but I can make some changes. |
Didn't realise that section existed but sure, I can take responsibility for fixing this. A large section of the docs are slightly out-of-date for sure and could do with a revamp. |
It's extremely stale now, so I just removed it in 9ffffa0 I've never figured out whether certifying transport layer keys matters much. I'm still pushing for it as a defense in depth, so presumably anything that goes here should discuss certifying transport layer keys, ala paritytech/substrate#6251 (comment) We should prioritize networking improvements that impact scalability however, so imho this could sit empty for a while. I'll mention it in https://github.com/w3f/research-security-issues/issues/26 |
https://github.com/w3f/research/blob/master/docs/polkadot/keys/4-secio.md
The document mentions scepticism about secio, and we've since then removed secio from the Substrate and Polkadot code bases.
Polkadot/Kusama right now are using the official libp2p noise.
The plan to try to use QUIC in the long term is still relevant, though.
@burdges I've been told to ping you!
The text was updated successfully, but these errors were encountered: