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

Quiet clients should only connect to Quiet-controlled non-Tor addresses #2753

Open
holmesworcester opened this issue Feb 19, 2025 · 0 comments
Open

Quiet clients should only connect to Quiet-controlled non-Tor addresses #2753

holmesworcester opened this issue Feb 19, 2025 · 0 comments
Labels
security

Comments

@holmesworcester
Copy link
Contributor

We haven't fully thought through the implications of people running their own non-Tor Quiet peers/servers, so Quiet clients should restrict usage of non-Tor addresses/server to domains or subdomains we control.
@holmesworcester holmesworcester moved this to Sprint in Quiet Feb 19, 2025
@islathehut islathehut moved this from Sprint to Backlog - Desktop & Backend in Quiet Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
security
Projects
Quiet
Status: Backlog - Desktop & Backend
Milestone
No milestone
Development

No branches or pull requests
1 participant
@holmesworcester