I will follow the development of uTox but I think it won't be easy to catch up with qTox & Isotoxin. a comparison table of Tox clients (outdated) 4_release/ - download page - releases - 圆4 6_release/ - download page - releases - x32 project page at GitHub - abandoned (the original developer of uTox is no longer involved) Second- uTox is really an alpha program- it is miles behind Isotoxin & qTox in terms of features and customization options. That doesn't make either Tox or Ring claiming decentralization/distributedness a lie at all, because they are decentralized and distributed.Today I did a brief testing of another Tox client, uTox (version 0.9.4 Alpha).įirst- uTox is not portable, it creates two files- tox_save.tox & utox_save in AppData ( C:\Users\UserName\AppData\Roaming\tox). With both Ring and Tox, anyway, other random users will see your IP, because that's the only way to connect to a DHT network in any P2P system. The only real difference here is that while Tox puts the communicating peers (you and your friend) in direct communication whenever they interact, which of course means letting each party know the other party's IP address, Ring makes text chat go through the DHT itself, which means your peer won't necessarily see your IP when you use text chat (but they will when you use audio or video). Ring is decentralized (actually, distributed, which goes further) to about the same extent as Tox. If you explicitly set up a separate SIP account, then it can behave as a SIP client, otherwise it will only connect to its OpenDHT with full encryption this sentence "Decentralized communication" which appears on top page description is a "lie"? Ring's SIP mode is separate from its P2P mode. This does not reflect reality of secure protocols, and actual security experts typically consider "DIY security" dangerous and rely on established primitives or even protocols.Īnd no, it's not just a matter of some theoretical loophole, but it's a functionality that Ring has built-in – after all, to be actually inter-operational with SIP, they have to have an option to remove security. ![]() Tox expose user's IP address by default (…)Ĭould you perhaps point out where is it "exposed" on the other hand seems to want to use "established standards", which are full of loopholes that strip out security. And no, it's not just a matter of some theoretical loophole, but it's a functionality that Ring has build-in – after all, to be actually inter-operational with SIP, they have to have an option to remove security.ĭunno, people don't generally to be concerned about security, and thus qTox tries to provide the best UX for people, and while doing so provide security. ![]() ![]() Ring, on the other hand seems to want to use "established standards", which are full of loopholes that strip out security. Tox has been build on a principle that there is only secure mode available. Third of all, the matter which you don't seem to be concerned about, is actual security. Second of all, either Ring has to also "expose" IPs, or is centralized, in which case their claim about being P2P can be thrown out of the window. It seems "Ring", on the other hand doesn't use IP as identifier.įirst of all, IP is not an identifier. Tox expose user's IP address by default(and the user need to use proxy such as Tor to mask IP).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |