So how exactly can you trace someone's IP through Tox and make sure that it is their IP without asking them for their IP or a hint to it (not because I want to trace the IPs of my contacts without asking them, but so that my method is more foolproof than just capturing packets and asking people which packet came or is going to them)? Or is this the wrong way of doing it? Though there was such a large amount of traffic (mostly UDP and TCP, but some ICMPs as well) that it was hard to really see anything. I then launched WireShark to try and see if I could capture some packets going to and from that port, however I could not find the IPs of any of my contacts (some had given me hints to parts of their IPs and I couldn't even find similar IPs). So I tried to see if I could find the IPs of some of my contacts (I ask for their prior permission), so I first figured out with netstat -tnap which port qTox was running on, the port was 33445. The user in the DHT, the IP address will only be discernible when the However, a userĬannot uncover another user's IP address using only a Tox ID to find Tunneling your Tox connections through Tor. Other users, as the whole point of peer-to-peer is to connect youĭirectly to your friends. Tox makes no attempt to cloak your IP address when communicating with Identity impossible to forge without stealing your personal private The form of meta-data, your IP address) from people who are not yourĪuthorized friends, enforcing Off-The-Record Messaging as the defaultĪnd only mode of operation for all messages, and by making your Tox protects your privacy by removing the need to rely on centralĪuthorities to provide messenger services, concealing your identity(In I am a user of Tox, my client is qTox (if that makes any difference), and I was just reading their FAQs section when I came across these sections:
0 Comments
Leave a Reply. |