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

The support for noise handshake protocol #4644

Open
1 task done
Gfuse opened this issue Mar 26, 2023 · 1 comment
Open
1 task done

The support for noise handshake protocol #4644

Gfuse opened this issue Mar 26, 2023 · 1 comment

Comments

@Gfuse
Copy link

Gfuse commented Mar 26, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Berty product

Mobile app

Feature request

Hello, Is there a possibility of adding support for the noise handshake protocol? In countries restricting internet connection, where a decentralized network like IPFS and Libp2p is more critical than ever, governments are tracking TLS handshake very well. At the same time, it has been tested that noise protocol works much better. So we will be glad to see an option on your app to choose between NOISE and TLS protocols or at least a build option to set the handshake protocol during a custom build.

Context

During the last year, more than 500 people have been killed in Iran, and more than 15000 people have been arrested, and the government is trying hard to isolate people and close the connection between their selves and the world. On the other side, we have been looking into various technologies that may help them connect securely. Because of this, we have tested the Libp2p network and IPFS and experienced that this solution works if we use a custom bootstrap node and noise protocol for the handshake. Since the Brety app already supports a custom bootstrap node, if you add this future, I am sure a lot of people in Iran will start to use this app to still connect.

Possible implementation

No response

@jefft0
Copy link
Collaborator

jefft0 commented Jul 7, 2023

Put in backlog for working on protocol enhancements in the near term.

@jefft0 jefft0 added the backlog label Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants