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.

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

Make configuration available without force to connect to Tox #10

Open
ovalseven8 opened this issue Oct 17, 2015 · 2 comments
Open

Make configuration available without force to connect to Tox #10

ovalseven8 opened this issue Oct 17, 2015 · 2 comments

Comments

@ovalseven8
Copy link
Contributor

Hello,

assume you would like to communicate anonymously with Tox over Tor.


At the moment (qTox):

  • Login
    • qTox connects to the Tox network
  • Go to the settings
  • Configure Tor as proxy (force TCP)

=> IP address is leaked

Desired behaviour (qTox):

  • Login (Offline-mode)
    • qTox just loads the profile but doesn't connect to the Tox network
  • Go to the settings
  • Configure Tor as proxy (force TCP)
  • Switch to 'online', 'busy' or 'away'
    • Only now qTox connects to the Tox network

=> IP address isn't leaked


So, what I wanted to say:
In Tox-Client-Standard should perhaps gets mentioned that you should be able to use Tox over Tor in a secure way.

  • Being able to change configuration without force to connect to Tox network
  • Being able to force TCP/proxy
@optimumtact
Copy link
Contributor

So some way to launch the client in a non connect mode so you can make proxy setting changes? I think thats a good idea, arguments can be made for recommendation/required, although I think recommended should be strong enough.

@tux3
Copy link

tux3 commented Dec 4, 2015

The current plan in qTox is to have a dropdown on the login window so you can pick your status from online/away/busy/offline before logging in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants