Skip to content
This repository has been archived by the owner on Apr 24, 2023. It is now read-only.

Insecure #116

Open
mkg20001 opened this issue Aug 30, 2017 · 8 comments
Open

Insecure #116

mkg20001 opened this issue Aug 30, 2017 · 8 comments
Labels
exp/expert Having worked on the specific codebase is important help wanted Seeking public contribution on this issue kind/bug A bug in existing code (including security flaws) status/ready Ready to be worked

Comments

@mkg20001
Copy link
Member

demo
Took me 5 min to write. Redirects all connections. Catches all dials.

Because I'm not evil I stop redirecting. But I could do that forever.

@mkg20001
Copy link
Member Author

mkg20001 commented Aug 30, 2017

Oh and btw: To crash the server just do io.emit("ss-handshake")

@daviddias
Copy link
Member

I was just explaining this to @lgierth yesterday. It's definitely not ideal. The initial plan (which continues to be) is to use a libp2p node for the rendezvous point that will authenticate all connections and so, instead of you announcing yourself, the node will node who is the real dialer.

@daviddias
Copy link
Member

@mkg20001 are you still running this?

@mkg20001
Copy link
Member Author

mkg20001 commented Aug 31, 2017

No but I might have crashed the server

@mkg20001
Copy link
Member Author

To fix it only 1 change is required: Add if (typeof offer != "object") return after function forwardHandshake(offer) {

@daviddias
Copy link
Member

@mkg20001 wanna contribute with that change and a test for it? :)

@Beanow
Copy link

Beanow commented Nov 19, 2017

So @mkg20001 if I understand correctly from your code in https://github.com/libp2p/js-libp2p-websocket-star-rendezvous the problem is that the ID needs to be proven, or you can assume another node's identity.

Wouldn't the leave endpoint need the same protection to protect against DOS attacks, as the discovery would give you all the IDs you need?

@mkg20001
Copy link
Member Author

Yes. WIll fix this in a moment.

@daviddias daviddias added status/ready Ready to be worked kind/bug A bug in existing code (including security flaws) help wanted Seeking public contribution on this issue exp/expert Having worked on the specific codebase is important labels Feb 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
exp/expert Having worked on the specific codebase is important help wanted Seeking public contribution on this issue kind/bug A bug in existing code (including security flaws) status/ready Ready to be worked
Projects
None yet
Development

No branches or pull requests

3 participants