Skip to content
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

remove Noise Pipes and padding within payloads #260

Merged
merged 2 commits into from
Apr 20, 2020
Merged

Conversation

yusefnapora
Copy link
Contributor

This PR removes Noise Pipes from the noise-libp2p spec, and also removes the padding within encrypted payloads.

Apologies to anyone who was waiting on this or was confused about the current state of the spec; this took me a lot longer than it should have :)

These changes bring the spec in line with the current Go and JavaScript implementations.

cc noise-libp2p IG: @raulk, @tomaka, @romanb, @shahankhatch, @Mikerah,
@djrtwo, @dryajov, @mpetrunic, @AgeManning, @morrigan, @araskachoi,
@mhchia

noise/README.md Outdated Show resolved Hide resolved
Co-Authored-By: Roman Borschel <[email protected]>
Comment on lines +172 to +174
noise-libp2p is initialized and used for all sessions. Implementations SHOULD
NOT store the static Noise key to disk, as there is no benefit and a hightened
risk of exposure.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reversing the suggestion makes sense now, as the handshake that would've benefitted from a long-lived/persisted key is now gone (the IK handshake).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants