-
Notifications
You must be signed in to change notification settings - Fork 41
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
Use nwaku's native wss #50
Comments
After review, ws works, however, most likely we want wss too (to be confirmed). |
Note that chrome blocks |
Ok so findings:
Hence this item needs to be tackle otherwise js-waku is not really useful in the browser. |
Most likely just use |
Blocked by libp2p/js-libp2p#931 |
Removed from milestone as wss is working (just not tested as part of CI). |
Thanks to the libp2p upgrade, waku actually tries to listen to a secure websocket. Using plain websocket for now, testing secure websocket is tracked with #50.
Blocked until nim-waku 0.7 with wss support is release. |
nim-waku v0.7 with native wss support is now released and used in the CI. |
Sounds very improbable that self-signed certificates can work. |
What I learned so far:
Further research: Now that I know how to make it work, I can test out self-signed certs. |
Further research:
|
Done. Some follow-up actions are tracked in #555 |
Problem
Browsers (Firefox, Chrome) only support secure websocket connections within an https page.
As most traffic nowadays defaults to https, it means we need to support wss.
nim-waku now supports native secure websocket. We need to confirm that js-waku can connect to it.
Definition of Done
Some/all mocha tests uses wss instead of wsWeb-chat example connects to Fleet via native websocket (use DNS discovery)blocked by enrtree's multiaddrs do not match SSL cert status-im/infra-nim-waku#38 Tracked with Use DNS Discovery by default #517Results
Waku.dial
always assumes store + relay protocols. Hence it fails if the remote node only has relay:Waku.dial
accepts protocols expected from the peer. Defaults to Waku Relay only. #516privkey.pem
andfullchain.pem
files created by letsencryptwss
connection within anhttp
page, even if the page is served on localhost and the errors are unhelpful.wss
connection using https://js-waku.wakuconnect.dev/examples/web-chat and the/connect
commandAll our examples use React and serve the page on http. It would be interesting to have at least one example setup to serve the page onhttps
. I was not able to do so by usingreact-scripts
. Not sure what would be the quickest way to achieve this.wss
in ahttp
page if thehttp
page is served by localhost.node key
for nim-waku so that the peer id does not change between two restarts. Doc: Document how to generate and store anodekey
nwaku#847ip4
multiaddr does not work, Chrome and Firefox reject self-signed certs.wss
connection is NOT shown to the user.[alt_names]\nIP.1
) does not work either (Firefox and Chrome reject self-signed certs).letsencrypt
Notes
The text was updated successfully, but these errors were encountered: