Open main menu

The Signal Protocol (formerly known as the TextSecure Protocol) is a non-federated cryptographic protocol that can be used to provide end-to-end encryption for voice calls, video calls,[3] and instant messaging conversations.[2] The protocol was developed by Open Whisper Systems in 2013[2] and was first introduced in the open-source TextSecure app, which later became Signal. Several closed-source applications claim to have implemented the protocol, such as WhatsApp, which is said to encrypt the conversations of "more than a billion people worldwide".[4] Facebook Messenger also say they offer the protocol for optional Secret Conversations, as does Skype for its Private Conversations.

Signal Protocol
Communication protocol
PurposeEnd-to-end encrypted communications
Developer(s)Signal Messenger
Based onOTR, SCIMP[1]
InfluencedOMEMO, Matrix[2]
OSI layerApplication layer
Websitesignal.org/docs,%20https://signal.org/

The protocol combines the Double Ratchet algorithm, prekeys, and a triple Elliptic-curve Diffie–Hellman (3-DH) handshake,[5] and uses Curve25519, AES-256, and HMAC-SHA256 as primitives.[6]

Contents

HistoryEdit

The Signal Protocol's development was started by Trevor Perrin and Moxie Marlinspike (Open Whisper Systems) in 2013. The first version of the protocol, TextSecure v1, was based on Off-the-Record Messaging (OTR).[7][8]

On 24 February 2014, Open Whisper Systems introduced TextSecure v2,[9] which migrated to the Axolotl Ratchet.[7][10] The design of the Axolotl Ratchet is based on the ephemeral key exchange that was introduced by OTR and combines it with a symmetric-key ratchet modeled after the Silent Circle Instant Messaging Protocol (SCIMP).[1] It brought about support for asynchronous communication ("offline messages") as its major new feature, as well as better resilience with distorted order of messages and simpler support for conversations with multiple participants.[11] The Axolotl Ratchet was named after the critically endangered aquatic salamander Axolotl, which has extraordinary self-healing capabilities. The developers refer to the algorithm as self-healing because it automatically disables an attacker from accessing the cleartext of later messages after having compromised a session key.[1]

The third version of the protocol, TextSecure v3, made some changes to the cryptographic primitives and the wire protocol.[7] In October 2014, researchers from Ruhr University Bochum published an analysis of TextSecure v3.[6][7] Among other findings, they presented an unknown key-share attack on the protocol, but in general, they found that it was secure.[12]

In March 2016, the developers renamed the protocol as the Signal Protocol. They also renamed the Axolotl Ratchet as the Double Ratchet algorithm to better differentiate between the ratchet and the full protocol[13] because some had used the name Axolotl when referring to the full protocol.[14][13]

As of October 2016, the Signal Protocol is based on TextSecure v3, but with additional cryptographic changes.[7] In October 2016, researchers from the UK's University of Oxford, Australia's Queensland University of Technology, and Canada's McMaster University published a formal analysis of the protocol.[15][16] They concluded that the protocol was cryptographically sound.[15][16]

PropertiesEdit

The protocol provides confidentiality, integrity, authentication, participant consistency, destination validation, forward secrecy, post-compromise security (aka future secrecy), causality preservation, message unlinkability, message repudiation, participation repudiation, and asynchronicity.[17] It does not provide anonymity preservation and requires servers for the relaying of messages and storing of public key material.[17]

The Signal Protocol also supports end-to-end encrypted group chats. The group chat protocol is a combination of a pairwise double ratchet and multicast encryption.[17] In addition to the properties provided by the one-to-one protocol, the group chat protocol provides speaker consistency, out-of-order resilience, dropped message resilience, computational equality, trust equality, subgroup messaging, as well as contractible and expandable membership.[17]

AuthenticationEdit

For authentication, users can manually compare public key fingerprints through an outside channel.[18] This makes it possible for users to verify each other's identities and avoid a man-in-the-middle attack.[18] An implementation can also choose to employ a trust on first use mechanism in order to notify users if a correspondent's key changes.[18]

MetadataEdit

The Signal Protocol does not prevent a company from retaining information about when and with whom users communicate.[19][20] There can therefore be differences in how messaging service providers choose to handle this information. Signal's privacy policy states that recipients' identifiers are only kept on the Signal servers as long as necessary in order to transmit each message.[21] In June 2016, Moxie Marlinspike told The Intercept: "the closest piece of information to metadata that the Signal server stores is the last time each user connected to the server, and the precision of this information is reduced to the day, rather than the hour, minute, and second."[20]

In October 2018, Signal Messenger announced that they had implemented a "sealed sender" feature into Signal, which reduces the amount of metadata that the Signal servers have access to by concealing the sender's identifier.[22][23] The sender's identity is conveyed to the recipient in each message, but is encrypted with a key that the server does not have.[23] This is done automatically if the sender is in the recipient's contacts or has access to their Signal Profile.[23] Users can also enable an option to receive "sealed sender" messages from non-contacts and people who do not have access to their Signal Profile.[23] A contemporaneous wiretap of the user's device and/or the Signal servers may still reveal that the device's IP address accessed a Signal server to send or receive messages at certain times.[22]

UsageEdit

Open Whisper Systems first introduced the protocol in their TextSecure app. They later merged an encrypted voice calling application called RedPhone into the TextSecure app and renamed it as Signal. RedPhone used ZRTP to encrypt its calls. In March 2017, Signal transitioned to a new WebRTC-based[3] calling system that also introduced the ability to make video calls.[24] Signal's new calling system uses the Signal Protocol for end-to-end encryption.[3]

In November 2014, Open Whisper Systems announced a partnership with WhatsApp to provide end-to-end encryption by incorporating the Signal Protocol into each WhatsApp client platform.[25] Open Whisper Systems said that they had already incorporated the protocol into the latest WhatsApp client for Android and that support for other clients, group/media messages, and key verification would be coming soon after.[26] On April 5, 2016, WhatsApp and Open Whisper Systems announced that they had finished adding end-to-end encryption to "every form of communication" on WhatsApp, and that users could now verify each other's keys.[27][28] In February 2017, WhatsApp announced a new feature, WhatsApp Status, which uses the Signal Protocol to secure its contents.[29]

In September 2015, G Data Software launched a new messaging app called Secure Chat which used the Signal Protocol.[30][31] G Data discontinued the service in May 2018.[32]

In September 2016, Google launched a new messaging app called Allo, which featured an optional Incognito Mode that used the Signal Protocol for end-to-end encryption.[33][34] In March 2019, Google discontinued Allo in favor of their Messages app on Android.[35][36]

In October 2016, Facebook deployed an optional mode called Secret Conversations in Facebook Messenger which provides end-to-end encryption using an implementation of the Signal Protocol.[37][38][39][40]

In January 2018, Open Whisper Systems and Microsoft announced the addition of Signal Protocol support to an optional Skype mode called Private Conversations.[41][42]

InfluenceEdit

The Signal Protocol has had an influence on other cryptographic protocols. In May 2016, Viber said that their encryption protocol is a custom implementation that "uses the same concepts" as the Signal Protocol.[43][44] Forsta's developers have said that their app uses a custom implementation of the Signal Protocol.[45][46][third-party source needed]

The Double Ratchet algorithm that was introduced as part of the Signal Protocol has also been adopted by other protocols. OMEMO is an XMPP Extension Protocol (XEP) that was introduced in the Conversations messaging app and approved by the XMPP Standards Foundation (XSF) in December 2016 as XEP-0384.[47][2] Matrix is an open communications protocol that includes Olm, a library that provides for optional end-to-end encryption on a room-by-room basis via a Double Ratchet algorithm implementation.[2] The developers of Wire have said that their app uses a custom implementation of the Double Ratchet algorithm.[48][49][50]

ImplementationsEdit

Signal Messenger maintains the following Signal Protocol libraries on GitHub:

See alsoEdit

ReferencesEdit

  1. ^ a b c Marlinspike, Moxie (26 November 2013). "Advanced cryptographic ratcheting". Signal Blog. Open Whisper Systems. Retrieved 23 September 2016.
  2. ^ a b c d e Ermoshina, Ksenia; Musiani, Francesca; Halpin, Harry (September 2016). "End-to-End Encrypted Messaging Protocols: An Overview". In Bagnoli, Franco; et al. (eds.). Internet Science. INSCI 2016. Florence, Italy: Springer. pp. 244–254. doi:10.1007/978-3-319-45982-0_22. ISBN 978-3-319-45982-0.
  3. ^ a b c Marlinspike, Moxie (14 February 2017). "Video calls for Signal now in public beta". Signal Blog. Open Whisper Systems. Retrieved 7 April 2017.
  4. ^ "Moxie Marlinspike - 40 under 40". Fortune. Time Inc. 2016. Retrieved 22 September 2016.
  5. ^ Unger et al. 2015, p. 241
  6. ^ a b Frosch et al. 2016
  7. ^ a b c d e Cohn-Gordon et al. 2016, p. 2
  8. ^ "Protocol". Open Whisper Systems. 2 March 2014. Archived from the original on 7 January 2015. Retrieved 28 October 2016 – via GitHub.
  9. ^ Donohue, Brian (24 February 2014). "TextSecure Sheds SMS in Latest Version". Threatpost. Retrieved 14 July 2016.
  10. ^ "ProtocolV2". Open Whisper Systems. 2 March 2014. Archived from the original on 15 October 2014. Retrieved 28 October 2016 – via GitHub.
  11. ^ Unger et al. 2015
  12. ^ Pauli, Darren (3 November 2014). "Auditors find encrypted chat client TextSecure is secure". The Register. Retrieved 4 November 2014.
  13. ^ a b Marlinspike, Moxie (30 March 2016). "Signal on the outside, Signal on the inside". Signal Blog. Open Whisper Systems. Retrieved 9 April 2016.
  14. ^ Cohn-Gordon et al. 2016, p. 1
  15. ^ a b Brook, Chris (10 November 2016). "Signal Audit Reveals Protocol Cryptographically Sound". Threatpost. Kaspersky Lab. Retrieved 11 November 2016.
  16. ^ a b Cohn-Gordon et al. 2016
  17. ^ a b c d Unger et al. 2015, p. 239
  18. ^ a b c Rottermanner et al. 2015, p. 5
  19. ^ Rottermanner et al. 2015, p. 4
  20. ^ a b Lee, Micah (22 June 2016). "Battle of the Secure Messaging Apps: How Signal Beats WhatsApp". The Intercept. Retrieved 8 October 2016.
  21. ^ "Privacy Policy". Open Whisper Systems. n.d. Retrieved 8 October 2016.
  22. ^ a b Dan Goodin (Oct 30, 2018). "New Signal privacy feature removes sender ID from metadata". Ars Technica. Retrieved 2019-03-28.
  23. ^ a b c d Lund, Joshua (29 October 2018). "Technology preview: Sealed sender for Signal". signal.org. Signal Messenger. Retrieved 16 April 2019.
  24. ^ Marlinspike, Moxie (13 March 2017). "Video calls for Signal out of beta". Signal Blog. Open Whisper Systems. Retrieved 7 April 2017.
  25. ^ Evans, Jon (18 November 2014). "WhatsApp Partners With Open Whisper Systems To End-To-End Encrypt Billions Of Messages A Day". TechCrunch. Retrieved 14 March 2016.
  26. ^ Marlinspike, Moxie (18 November 2014). "Open Whisper Systems partners with WhatsApp to provide end-to-end encryption". Open Whisper Systems. Retrieved 14 March 2016.
  27. ^ Metz, Cade (5 April 2016). "Forget Apple vs. the FBI: WhatsApp Just Switched on Encryption for a Billion People". Wired. Retrieved 5 April 2016.
  28. ^ Lomas, Natasha (5 April 2016). "WhatsApp completes end-to-end encryption rollout". TechCrunch. Retrieved 5 April 2016.
  29. ^ "WhatsApp Status". WhatsApp. Facebook. 20 February 2017.
  30. ^ Seals, Tara (17 September 2015). "G DATA Adds Encryption for Secure Mobile Chat". Infosecurity Magazine. Retrieved 14 July 2016.
  31. ^ "SecureChat". G Data. Retrieved 14 July 2016 – via GitHub.
  32. ^ "G DATA Secure Chat wird eingestellt" (in German). G DATA Software AG. 18 May 2018. Retrieved 26 April 2019.
  33. ^ Greenberg, Andy (18 May 2016). "With Allo and Duo, Google Finally Encrypts Conversations End-to-End". Wired. Retrieved 18 May 2016.
  34. ^ Gibbs, Samuel (21 September 2016). "Google launches WhatsApp competitor Allo – with Google Assistant". The Guardian. Retrieved 21 September 2016.
  35. ^ Porter, Jon (12 March 2019). "Google is finally saying goodbye to Allo today". The Verge. Vox Media. Retrieved 26 April 2019.
  36. ^ Klainer, Matt (5 December 2018). "The latest on Messages, Allo, Duo and Hangouts". Google. Retrieved 26 April 2019.
  37. ^ Isaac, Mike (8 July 2016). "Facebook to Add 'Secret Conversations' to Messenger App". The New York Times. Retrieved 12 July 2016.
  38. ^ "Messenger Starts Testing End-to-End Encryption with Secret Conversations". Facebook. 8 July 2016. Retrieved 11 January 2018.
  39. ^ Greenberg, Andy (8 July 2016). "'Secret Conversations:' End-to-End Encryption Comes to Facebook Messenger". Wired. Retrieved 12 July 2016.
  40. ^ Greenberg, Andy (4 October 2016). "You Can All Finally Encrypt Facebook Messenger, So Do It". Wired. Retrieved 5 October 2016.
  41. ^ Newman, Lily Hay (11 January 2018). "Skype's Rolling Out End-to-End Encryption For Hundreds of Millions of People". Wired. Retrieved 13 January 2018.
  42. ^ Lund, Joshua (11 January 2018). "Signal partners with Microsoft to bring end-to-end encryption to Skype". Signal Blog. Open Whisper Systems. Retrieved 13 January 2018.
  43. ^ "Viber Encryption Overview". Viber. 3 May 2016. Archived from the original on 11 July 2016. Retrieved 8 July 2017.
  44. ^ Eyal, Ofir (3 May 2016). "Canada, Germany and Australia are getting e2e encryption". Viber. Retrieved 9 October 2016.
  45. ^ u/tooker. "r/crypto - Forsta - Signal based messaging platform for enterprises". reddit. Retrieved 2019-02-06.
  46. ^ "ForstaLabs/libsignal-node". GitHub. Forsta Inc. 2019-02-03. Retrieved 2019-02-06.
  47. ^ Andreas Straub (7 December 2016). "XEP-0384: OMEMO Encryption". XMPP Standards Foundation website. Retrieved 28 April 2017.
  48. ^ "Add attribution". GitHub. Wire Swiss GmbH. 9 May 2016. Retrieved 9 October 2016.
  49. ^ "Wire Security Whitepaper" (PDF). Wire Swiss GmbH. 3 March 2016. Retrieved 7 February 2019.
  50. ^ Lomas, Natasha (16 December 2016). "Encrypted messaging app Wire adds usernames so you can limit what you share with contacts". TechCrunch. Verizon Media. Retrieved 8 February 2019.

LiteratureEdit

  • Cohn-Gordon, Katriel; Cremers, Cas; Dowling, Benjamin; Garratt, Luke; Stebila, Douglas (25 October 2016). "A Formal Security Analysis of the Signal Messaging Protocol" (PDF). Cryptology ePrint Archive. International Association for Cryptologic Research (IACR).
  • Ermoshina, Ksenia; Musiani, Francesca; Halpin, Harry (September 2016). "End-to-End Encrypted Messaging Protocols: An Overview". In Bagnoli, Franco; et al. (eds.). Internet Science. INSCI 2016. Florence, Italy: Springer. pp. 244–254. doi:10.1007/978-3-319-45982-0_22. ISBN 978-3-319-45982-0.
  • Frosch, Tilman; Mainka, Christian; Bader, Christoph; Bergsma, Florian; Schwenk, Jörg; Holz, Thorsten (March 2016). How Secure is TextSecure?. 2016 IEEE European Symposium on Security and Privacy (EuroS&P). Saarbrücken, Germany: IEEE. pp. 457–472. doi:10.1109/EuroSP.2016.41. ISBN 978-1-5090-1752-2. Retrieved 28 September 2016.
  • Rottermanner, Christoph; Kieseberg, Peter; Huber, Markus; Schmiedecker, Martin; Schrittwieser, Sebastian (December 2015). Privacy and Data Protection in Smartphone Messengers (PDF). Proceedings of the 17th International Conference on Information Integration and Web-based Applications & Services (iiWAS2015). ACM International Conference Proceedings Series. ISBN 978-1-4503-3491-4. Retrieved 25 September 2016.
  • Unger, Nik; Dechand, Sergej; Bonneau, Joseph; Fahl, Sascha; Perl, Henning; Goldberg, Ian Avrum; Smith, Matthew (2015). SoK: Secure Messaging (PDF). Proceedings of the 2015 IEEE Symposium on Security and Privacy. IEEE Computer Society's Technical Committee on Security and Privacy. pp. 232–249. doi:10.1109/SP.2015.22.

External linksEdit