-
Notifications
You must be signed in to change notification settings - Fork 446
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
go-js echo / plaintext fails to send message #1110
Comments
@gitaaron what is the problem / use case you are trying to solve? |
hi @lidel thanks for looking at this! The use case is to assist in development/debugging go-js interop issues. Here is a little more context in case it is helpful. I was looking at go-js webrtc interop which I believe is still an issue tagged with help wanted. To assist myself in debugging the problem I figured it might help to look at the traffic over wireshark. This is when I discovered the go-js interop issue over plaintext (more specifically the discrepancy in the exchange object passed). So I figured I might create a new issue and submit a PR with the fix in case someone else might also find it useful. I am new to libp2p so your feedback/advice is appreciated. |
linked to #1111 |
Triage notes: @gitaaron could you try with latest version and Plaintext encryption? |
Unfortunately, still not working for me. When I try to dial from Go to JS over plaintext echo I see the following error msg in Go -
When I try to dial JS to Go I see the following error message -
Last I looked into it there was a mismatch in the protobuf 'Exchange' message where on the JS side the 'pubkey' seemed to be nested as an additional Exchange. |
Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days. |
Closing as stale |
Severity: Medium
Description:
I tried to dial the JS echo listener example from the Go echo dialer example and vice versa over plaintext and in both cases it failed during the handshake.
It seems that the Data property of the pubkey in Exchange is inconsistent where Go simply uses the marshalled value of the encrypted public key and JS includes the entire pubkey object re-encoded as a protobuf.
There also seems to be an issue with the samples themselves where the Go sample uses newline to signify the end of a message and JS does not.
Steps to reproduce the error:
> node listener
> ./echo -l 9012 -d /ip4/127.0.0.1/tcp/10333/p2p/QmcrQZ6RJdpYuGvZqD5QEHAv6qX4BrQLJLQPQUrTrzdcgm -insecure
The text was updated successfully, but these errors were encountered: