Specifically, Tox employs Curve25519 for its key exchanges, xsalsa20 for symmetric encryption, and Poly1305 for MACs. Tox uses the cryptographic primitives present in the NaCl crypto library, via libsodium.
Tox uses the Opus audio format for audio streaming and the VP8 video compression format for video streaming. Implementations of the Tox protocol not done by the project exist. The core of Tox is an implementation of the Tox protocol, an example of the application layer of the OSI model and arguably the presentation layer. Technical documents describing the design of the Core, written by the core developer irungentoo, are available publicly. Anyone can create a client utilizing the core. User front-ends, or clients, are built on the top of the core. The Tox core is a library establishing the protocol and API. The Tox enabled messengers deal with this in separate ways, some prevent the user from sending the message if the other party has disconnected while others show the message as being sent when in reality it is stored in the sender's phone waiting to be delivered when the receiving party reconnects to the network. Though several apps that use the Tox protocol seem similar in function to regular instant messaging apps, the lack of central servers similar to XMPP or Matrix currently has the consequence that both parties of the chat need to be online for the message to be sent and received. Screenshot of the qTox messenger, which uses the Tox protocol, a message has been sent by "Joeri" while the receiving party is offline, the client shows the user that the message is still in transit, when in reality the qTox client is waiting for the receiver of the message to come back online Client developers are strongly encouraged to adhere to the Tox Client Standard in order to maintain cross-client compatibility and uphold best security practices. Features that are not related to the core networking system are left up to the client. Additional features can be implemented by any client as long as they are supported by the core protocol. Tox clients aim to provide support for various secure and anonymised communication features while every client supports messaging, additional features like group messaging, voice and video calling, voice and video conferencing, typing indicators, message read-receipts, file sharing, profile encryption, and desktop streaming are supported to various degrees by mobile and desktop clients. However, a non-friend user cannot easily discover your IP address using only a Tox ID you reveal your IP address to someone only when you add them to your contacts list. A workaround does exist in the form of tunneling your Tox connections through Tor. Tox makes no attempt to cloak your IP address when communicating with friends, as the whole point of a peer-to-peer network is to connect you directly to your friends. All traffic over Tox is end-to-end encrypted using the NaCl library, which provides authenticated encryption and perfect forward secrecy. Users have the ability to message friends, join chat rooms with friends or strangers, voice/video chat, and send each other files. Users are assigned a public and private key, and they connect to each other directly in a fully distributed, peer-to-peer network.
QTOX USER LIST DOWNLOAD
On July 12, 2014, Tox entered an alpha stage in development and a redesigned download page was created for the occasion.įeatures Encryption of traffic Pre-alpha testing binaries were made available for users from February 3, 2014, onward.
The initial commit to GitHub was pushed on June 23, 2013, by a user named irungentoo.
0 kommentar(er)
