Better Late Than Never - WhatsApp Is Using End-to-End Encryption – Finally!

The article is written by Filip Chytry, Mobile Threat Intelligence Manager from Avast.

Can you imagine leaving your house without locking the main door? I guess not. Locking the door is a routine that we do automatically. So why there is so much noise about the latest update from WhatsApp as if the company has just reinvented communication encryption?

What is End-to-End encryption

End-to-End encryption (E2EE) is a system of communication where only the people who are communicating can read the messages. No eavesdropper can access the cryptographic keys needed to decrypt the conversation, including telecom providers, Internet providers and the company that runs the messaging service. Theoretically, that means nobody else can access your transmitted data even if and when they can intercept the traffic.

This is like using a house key and not leaving the door open, isn't it? The same standard should be followed by any App or service communicating from of your device no matter what kind of data you are transmitting.

How does End-to-End encryption technically work in WhatsApp?

To communicate with another WhatsApp user, a WhatsApp client first needs to establish an encrypted session. Once the session is established, clients do not need to rebuild a new session with each other until the existing session state is lost through an external event such as an app reinstall or device change.

To establish a session:

  1. The initiating client (“initiator”) requests the public Identity Key, public Signed Pre Key, and a single public One-Time Pre Key for the recipient.
  2. The server returns the requested public key values. A One-Time Pre Key is only used once, so it is removed from server storage after being requested. If the recipient’s latest batch of One-Time Pre Key has been consumed and the recipient has not replenished them, no One-Time Pre Key will be returned.
  3. The initiator saves the recipient’s Identity Key as Irecipient, the Signed Pre Key as Srecipient, and the One-Time Pre Key as Orecipient.
  4. The initiator generates an ephemeral Curve25519 key pair, Einitiator.
  5. The initiator loads its own Identity Key as Iinitiator.
  6. The initiator calculates a master secret as master_secret = ECDH(Iinitiator, Srecipient) || ECDH(Einitiator, Irecipient) || ECDH(Einitiator, Srecipient) || ECDH(Einitiator, Orecipient) If there is no One Time Pre Key, the final ECDH is omitted.
  7. The initiator uses HKDF (Extract-and-Expand Key ) to create a Root Key and Chain Keys from the master_secret.

Exchanging Messages

Once a session has been established, clients exchange messages that are protected with a Message Key using AES256 in CBC mode for encryption and HMAC-SHA256 for authentication.

The Message Key changes for each message transmitted, and is ephemeral, such that the Message Key used to encrypt a message cannot be reconstructed from the session state after a message has been transmitted or received.

The Message Key is derived from a sender’s Chain Key that “ratchets” forward with every message sent. Additionally, a new ECDH agreement is performed with each message roundtrip to create a new Chain Key. This provides forward secrecy through the combination of both an immediate “hash ratchet” and a round trip “DH ratchet.”

Let's make it a little bit simpler

What happens after this process is that each device on one side A and B have exchanged private keys which are unique for each session and each user. If we compare this situation to keys from your home, it means each time you go home, you will have a new key in your pocket, but all exchanges will be done automatically without you being involved.

Why is WhatsApp's end-to-end encryption not such a big step forward?

I know immediately this is big news, but don't you think your privacy should be protected from the very beginning once you are actually installing any application? I can understand when some early-stage startups can't afford to have encryption implemented properly while they are starting out. However, a company with the size and reputation of WhatsApp should already have end-to-end encryption implemented a long time ago.

Luckily these days, we have companies like TL that are trying to move security standards closer to people and make them more affordable for everyone. So if you are an App developer or service provider, you can use pre-built end-to-end encryption solution which is ready straight out of the box.

Request a FREE Demo or visit www.teskalabs.com/products/seacat-mobile-secure-gateway to learn more about TeskaLabs Application Security technology and how we can help you with the security of your mobile app and its backend systems.

About the Author

Guest Author

A guest author is an SME of his/her topics or a friend of TeskaLabs.


TurboCat.io

Data encryption tool for GDPR

More information


You Might Be Interested in Reading These Articles

Online Fraud Is Increasing - Is Business Intelligence the Answer?

With the year on year rise in ecommerce, there is a corresponding rise in online fraud - in fact, according to Financial Fraud Action UK, this type of activity had increased by a quarter to £399.5 million in the first half of 2016. The most recent manifestation of this is the concept of “testing” - this is where the criminals try small purchases to check the validity of card details, before moving in for the kill.

Continue reading ...

security

Published on July 04, 2017

Business Intelligence and Mobile App Security

We are a security Cat, specializing in mobile application security. You know that. In the last couple of months, we happened to stumble onto another tech domain: Business Intelligence (BI).

Continue reading ...

business-intelligence security

Published on December 26, 2014

Why Developers Are Boosting Up Their Mobile Application Security?

Mobile application security is a significant issue for developers. Most try their best to make mobile apps secure and safe for their users. Here are some of the other reasons why developers are boosting up their mobile application security.

Continue reading ...

security development

Published on April 14, 2015