Serious privacy protection must include both protection of content and protection of metadata. Phone number and/or email address to one’s Threema ID is optional.Īll data involved in communication other than the actual content is metadata. Instead of a phone number, the Threema ID (a randomly generated eight-digit string) serves as unique identifier. Threema can be used without providing any personal information whatsoever. For more details and how to activate the feature, please refer to this FAQ entry.įor detailed technical information about the cryptography in Threema, read the Cryptography Whitepaper.Ĭomprehensive privacy protection requires solid message encryption, but there is more to it. Perfect Forward Secrecy: Threema supports Perfect Forward Secrecy. A 128 bit message authentication code (MAC) is also added to each message to The stream cipher XSalsa20 is then used to encrypt the message. NIST estimate (page 54), this corresponds at least with the strength provided by 2048 bit RSA.ĮCDH on Curve25519 is used in conjunction with a hash function and a random nonce to derive a unique 256 bit Strength of the encryption: The asymmetric ECC based encryption used by Threema has a strength of 255 bits. This guarantees that no third party – not even the server operators – can decrypt the content of the messages and calls. on a public wireless network) cannot even learn who is logging in and who is communicating with whom.Īll encryption and decryption happens directly on the device, and the user is in control over the key exchange. To ensure that an adversary who captures network packets (e.g. There are two layers of encryption: The end-to-end layer between the conversation participants, and an additional layer to protect against eavesdropping of the connection between the app and the servers. Since the Threema apps are open source, anyone knowledgeable enough can confirm Threema’s security.
Threema uses tried-and-tested asymmetric cryptography to protect messages and calls between sender and recipient (and the communication between the app and the servers).
0 kommentar(er)
