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.

Sign up for GitHub

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

Jump to bottom

JS and Go cannot connect when using non-RSA keys #373

Closed
tobowers opened this issue Jun 28, 2019 · 2 comments
Closed

JS and Go cannot connect when using non-RSA keys #373

tobowers opened this issue Jun 28, 2019 · 2 comments
Labels
exp/wizard Extensive knowledge (implications, ramifications) required kind/bug A bug in existing code (including security flaws) P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked

Comments

@tobowers
Copy link
Contributor

  • Version: JS: 0.25.4, GO: 0.2.0
  • Platform: JS & GO interplay
  • Subsystem: Just connection, so I suppose Swarm?

Type: Bug

Severity: High

Description:

See description here: https://discuss.libp2p.io/t/browser-go-bootstrap-and-connect/175 .

Javascript and GO cannot connect over websockets when using non-RSA keys.

Steps to reproduce the error:

I'm sorry to not have a minimal reproduction already established, but you need a running go node using an ecdsa key and then javascript will not be able to connect to it over web sockets.
@aknuds1
Copy link
Contributor

aknuds1 commented Jul 1, 2019 •
edited
Loading

I'm looking into solving this. Using this issue as starting point.

@jacobheun jacobheun added kind/bug A bug in existing code (including security flaws) exp/wizard Extensive knowledge (implications, ramifications) required P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked labels Jul 1, 2019
@vasco-santos
Copy link
Member

This seems to not be the case anymore, since the interop tests are doing it now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
exp/wizard Extensive knowledge (implications, ramifications) required kind/bug A bug in existing code (including security flaws) P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@tobowers @aknuds1 @jacobheun @vasco-santos