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

Libp2p is listening on 0:0:0:0 and globally reachable #1925

Open
holmesworcester opened this issue Oct 5, 2023 · 1 comment
Open

Libp2p is listening on 0:0:0:0 and globally reachable #1925

holmesworcester opened this issue Oct 5, 2023 · 1 comment
Labels
bug Something isn't working security

Comments

@holmesworcester
Copy link
Contributor

holmesworcester commented Oct 5, 2023 •
edited
Loading

Right now, Tor onion address incoming connections are forwarded to libp2p, which listens on 0:0:0:0. Instead, it should listen on 127.0.0.1 or in such a way that it is only reachable by Tor.
@holmesworcester holmesworcester converted this from a draft issue Oct 5, 2023
@holmesworcester holmesworcester changed the title Libp2p websocket is listening on 0:0:0:0 and globally reachable Libp2p is listening on 0:0:0:0 and globally reachable Oct 5, 2023
@holmesworcester holmesworcester added the bug Something isn't working label Oct 5, 2023
@holmesworcester holmesworcester moved this from Backlog - Desktop & Backend to Next Sprint in Quiet Oct 6, 2023
@holmesworcester
Copy link
Contributor Author

#1897 mitigates this and should make it impossible to connect to peers but we should still fix this.

@holmesworcester holmesworcester moved this from Next Sprint to Backlog - Desktop & Backend in Quiet Oct 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working security
Projects
Quiet
Status: Backlog - Desktop & Backend
Milestone
No milestone
Development

No branches or pull requests
1 participant
@holmesworcester