Jump to content


From Wikipedia, the free encyclopedia
Original author(s)Moxie Marlinspike
and Stuart Anderson
(Whisper Systems)
Developer(s)Open Whisper Systems and community
Initial releaseMay 25, 2010 (2010-05-25)[1]
Final release
(September 29, 2015; 8 years ago (2015-09-29))[2]
Written inJava (client and server)
Operating systemAndroid
Successormerged with RedPhone to become Signal[3]
Size11 MB
Available in34 languages[4]
TypeEncrypted instant messaging
LicenseGPLv3 (client),[5]
AGPLv3 (server)[6]

TextSecure was an encrypted messaging application for Android that was developed from 2010 to 2015. It was a predecessor to Signal and the first application to use the Signal Protocol, which has since been implemented into WhatsApp and other applications. TextSecure used end-to-end encryption to secure the transmission of text messages, group messages, attachments and media messages to other TextSecure users.

TextSecure was first developed by Whisper Systems, who were later acqui-hired by Twitter. The application's source code was then released under a free and open-source software license. In 2013, TextSecure's development was picked up by an independent group called Open Whisper Systems, who merged it with an encrypted voice calling application called RedPhone and renamed the product as Signal.


TextSecure's icon from May 2010 to February 2014 and from February 2014 to February 2015.

Whisper Systems and Twitter (2010–2011)[edit]

TextSecure started as an application for sending and receiving encrypted SMS messages.[7] Its beta version was first launched on May 25, 2010, by Whisper Systems,[1] a startup company co-founded by security researcher Moxie Marlinspike and roboticist Stuart Anderson.[8][9] In addition to launching TextSecure, Whisper Systems produced a firewall, tools for encrypting other forms of data, and RedPhone, an application that provided encrypted voice calls.[1][8] All of these were proprietary enterprise mobile security software.

In November 2011, Whisper Systems announced that it had been acquired by Twitter. The financial terms of the deal were not disclosed by either company.[10] The acquisition was done "primarily so that Mr. Marlinspike could help the then-startup improve its security".[11] Shortly after the acquisition, Whisper Systems' RedPhone service was made unavailable.[12] Some criticized the removal, arguing that the software was "specifically targeted [to help] people under repressive regimes" and that it left people like the Egyptians in "a dangerous position" during the events of the 2011 Egyptian revolution.[13]

Twitter released TextSecure as free and open-source software under the GPLv3 license in December 2011.[8][14][15][16] RedPhone was also released under the same license in July 2012.[17] Marlinspike later left Twitter and founded Open Whisper Systems as a collaborative Open Source project for the continued development of TextSecure and RedPhone.[18][19]

Open Whisper Systems (2013–2015)[edit]

A timeline of the development of TextSecure.
a) Addition of encrypted group chat and instant messaging capabilities.
b) End of encrypted SMS/MMS messaging, which prompted the creation of a fork.
c) RedPhone merged into TextSecure and it was renamed as Signal.
d) Signal as a RedPhone counterpart for iOS.
e) Addition of encrypted group chat and instant messaging capabilities on iOS.

Open Whisper Systems' website was launched in January 2013.[19] Open Whisper Systems started working to bring TextSecure to iOS in March 2013.[20][21]

In February 2014, Open Whisper Systems introduced the second version of their TextSecure Protocol (now Signal Protocol), which added group chat and push messaging capabilities to TextSecure.[20][22] Toward the end of July 2014, Open Whisper Systems announced plans to unify its RedPhone and TextSecure applications as Signal.[23] This announcement coincided with the initial release of Signal as a RedPhone counterpart for iOS. The developers said that their next steps would be to provide TextSecure instant messaging capabilities for iOS, unify the RedPhone and TextSecure applications on Android, and launch a web client.[24] Signal was the first iOS app to enable easy, strongly encrypted voice calls for free.[18][25]

TextSecure compatibility was added to the iOS application in March 2015.[26][27] Later that month, Open Whisper Systems ended support for sending and receiving encrypted SMS/MMS messages on Android. From version 2.7.0 onward, TextSecure only supported sending and receiving encrypted messages via the data channel. Reasons for this included:[7]

  • Complications with the SMS encryption procedure: Users needed to manually initiate a "key exchange", which required a full round trip before any messages could be exchanged. In addition to this, users could not always be sure whether the receiver could receive encrypted SMS/MMS messages or not.
  • Compatibility issues with iOS: Not possible to send or receive encrypted SMS/MMS messages on iOS due to the lack of APIs.
  • The large amounts of metadata that inevitably arise and are uncontrollable when using SMS/MMS for the transportation of messages.
  • Focus on software development: Maintaining SMS/MMS encryption and dealing with edge cases took up valuable resources and inhibited the development of the software.

Open Whisper Systems' abandonment of SMS/MMS encryption prompted some users to create a fork named Silence (initially called SMSSecure[28]) that is meant solely for the encryption of SMS and MMS messages.[29][30]

In November 2015, the RedPhone application was merged into TextSecure and it was renamed as Signal for Android.[3]


The application prevented screenshots of conversations by default. Its intention was to prevent other applications from taking screenshots.[31]

TextSecure allowed users to send encrypted text messages, audio messages, photos, videos, contact information, and a wide selection of emoticons over a data connection (e.g. Wi-Fi, 3G or 4G) to other TextSecure users with smartphones running Android. TextSecure also allowed users to exchange unencrypted SMS and MMS messages with people who did not have TextSecure.[22]

Messages sent with TextSecure to other TextSecure users were automatically end-to-end encrypted, which meant that they could only be read by the intended recipients. The keys that were used to encrypt the user's messages were stored on the device alone. In the user interface, encrypted messages were denoted by a lock icon.

TextSecure allowed the user to set a passphrase that encrypted the local message database and the user's encryption keys.[32] This did not encrypt the user's contact database or message timestamps.[32] The user could define a time period after which the application "forgot" the passphrase, providing an additional protection mechanism in case the phone was lost or stolen.[31]

TextSecure had a built-in function for verifying that the user was communicating with the right person and that no man-in-the-middle attack had occurred. This verification could be done by comparing key fingerprints (in the form of QR codes) in person.[31] The application would also notify the user if the correspondent's key fingerprint had changed.[31]

TextSecure allowed users to chat with more than one person at a time.[33] Group chats were automatically end-to-end encrypted and held over an available data connection if all participants were registered TextSecure users. Users could create groups with a title and avatar icon, add their friends, join or leave groups, and exchange messages/media, all with the same encryption properties pairwise TextSecure chats provided. The servers did not have access to group metadata such as lists of group members, the group title, or the group avatar icon.[22][34]

The application could also function as a drop-in replacement for Android's native messaging application as it could fall back to sending unencrypted SMS and MMS messages.


TextSecure required that the user had a phone number for verification.[35] The number did not have to be the same as on the device's SIM card; it could also be a VoIP number[35] or a landline as long as the user could receive the verification code and have a separate device to set-up the software. A number could only be registered to one device at a time.

The official TextSecure client required Google Play Services because the app was dependent on Google's GCM push messaging framework.[36] From February 2014 to March 2015, TextSecure used GCM as the transport for message delivery over the data channel. From March 2015 forward, TextSecure's message delivery was done by Open Whisper Systems themselves and the client relied on GCM only for a wakeup event.[7]


Encryption protocol[edit]

TextSecure was the first application to use the Signal Protocol (then called the TextSecure Protocol), which has since been implemented into WhatsApp, Facebook Messenger, and Google Allo, encrypting the conversations of "more than a billion people worldwide".[37] The protocol combines the Double Ratchet Algorithm, prekeys, and a 3-DH handshake.[38] It uses Curve25519, AES-256, and HMAC-SHA256 as primitives.[39]

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

The group chat protocol is a combination of a pairwise double ratchet and multicast encryption.[40] 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.[40]


All client-server communications were protected by TLS.[41] Once the server removed this layer of encryption, each message contained either the phone number of the sender or the receiver in plaintext.[42] This metadata could in theory have allowed the creation of "a detailed overview on when and with whom users communicated".[42] Open Whisper Systems asserted that their servers did not keep this metadata.

In order to determine which contacts were also TextSecure users, cryptographic hashes of the user's contact numbers were periodically transmitted to the server.[43] The server then checked to see if those matched any of the SHA256 hashes of registered users and told the client if any matches were found.[43] Moxie Marlinspike wrote that it is easy to calculate a map of all possible hash inputs to hash outputs and reverse the mapping because of the limited preimage space (the set of all possible hash inputs) of phone numbers, and that "practical privacy preserving contact discovery remains an unsolved problem".[42][43]

The group messaging mechanism was designed so that the servers did not have access to the membership list, group title, or group icon.[44] Instead, the creation, updating, joining, and leaving of groups was done by the clients, which delivered pairwise messages to the participants in the same way that one-to-one messages were delivered.[22][34]

The server architecture was partially decentralized between December 2013 and February 2016. In December 2013, it was announced that the messaging protocol that was used by TextSecure had successfully been integrated into the Android-based open-source operating system CyanogenMod.[45][46][47] From CyanogenMod 11.0 onward, the client logic was contained in a system app called WhisperPush. According to Open Whisper Systems, the Cyanogen team ran their own TextSecure server for WhisperPush clients, which federated with Open Whisper Systems' TextSecure server, so that both clients could exchange messages with each-other seamlessly.[47] The CyanogenMod team discontinued WhisperPush in February 2016, and recommended that its users switch to Signal.[48]


The complete source code of TextSecure was available on GitHub under a free software license.[5] The software that handled message routing for the TextSecure data channel was also open source.[6]


TextSecure was officially distributed only through Google Play. In October 2015, TextSecure had been installed over 1 000 000 times through Google Play.[2]

TextSecure was briefly included in the F-Droid software repository in 2012, but was removed at the developer's request because it was an unverified build and exceptionally out of date. Open Whisper Systems have subsequently said that they will not support their applications being distributed through F-Droid because it does not provide timely software updates, relies on a centralized trust model and necessitates allowing the installation of apps from unknown sources which harms Android's security for average users.[36]


In October 2013, iSEC Partners published a blog post in which they said that they had audited several of the projects supported by the Open Technology Fund over the past year, including TextSecure.[49]

In October 2014, researchers from Ruhr University Bochum published an analysis of the TextSecure encryption protocol.[39] Among other findings, they presented an unknown key-share attack on the protocol, but in general, they found that the encrypted chat client was secure.[50]


Former NSA contractor Edward Snowden endorsed TextSecure on multiple occasions. In his keynote speech at SXSW in March 2014, he praised TextSecure for its ease-of-use.[51][52] During an interview with The New Yorker in October 2014, he recommended using "anything from Moxie Marlinspike and Open Whisper Systems".[53] Asked about encrypted messaging apps during a Reddit AMA in May 2015, he recommended TextSecure.[54][55]

In October 2014, the Electronic Frontier Foundation (EFF) included TextSecure in their updated Surveillance Self-Defense guide.[56] In November 2014, TextSecure received a perfect score on the EFF's Secure Messaging Scorecard.[57][58] TextSecure received points for having communications encrypted in transit, having communications encrypted with keys the providers don't have access to (end-to-end encryption), making it possible for users to independently verify their correspondent's identities, having past communications secure if the keys are stolen (forward secrecy), having their code open to independent review (open-source), having their security designs well-documented, and having recent independent security audits.[57] At the time, "ChatSecure + Orbot", Cryptocat, "Signal / RedPhone", Pidgin (with OTR), Silent Phone, Silent Text, and Telegram's optional secret chats also received seven out of seven points on the scorecard.[57]

Developers and funding[edit]

TextSecure was developed by a nonprofit software group called Open Whisper Systems.[59] The group is funded by a combination of donations and grants, and all of its products are published as free and open-source software.

As of October 2016, the project has received an unknown amount of donations from individual sponsors via the Freedom of the Press Foundation.[60] Open Whisper Systems has received grants from the Knight Foundation,[61] the Shuttleworth Foundation,[62] and the Open Technology Fund,[63] a U.S. government funded program that has also supported other privacy projects like the anonymity software Tor and the encrypted instant messaging app Cryptocat.

See also[edit]


  1. ^ a b c Greenberg, Andy (25 May 2010). "Android App Aims to Allow Wiretap-Proof Cell Phone Calls". Forbes. Archived from the original on 21 January 2012. Retrieved 28 February 2014.
  2. ^ a b "TextSecure Private Messenger". Google Play. Archived from the original on 19 October 2015. Retrieved 19 October 2015.
  3. ^ a b Marlinspike, Moxie (2 November 2015). "Just Signal". Open Whisper Systems. Retrieved 2 November 2015.
  4. ^ Open Whisper Systems. "List of languages supported by TextSecure". GitHub. Retrieved 15 March 2014.
  5. ^ a b Open Whisper Systems. "TextSecure". GitHub. Retrieved 26 February 2014.
  6. ^ a b Open Whisper Systems. "TextSecure-Server". GitHub. Retrieved 2 March 2014.
  7. ^ a b c Open Whisper Systems (6 March 2015). "Saying goodbye to encrypted SMS/MMS". Retrieved 22 March 2015.
  8. ^ a b c Garling, Caleb (2011-12-20). "Twitter Open Sources Its Android Moxie | Wired Enterprise". Wired. Retrieved 2011-12-21.
  9. ^ "Company Overview of Whisper Systems Inc". Bloomberg Businessweek. Archived from the original on March 4, 2014. Retrieved 2014-03-04.
  10. ^ Tom Cheredar (November 28, 2011). "Twitter acquires Android security startup Whisper Systems". VentureBeat. Retrieved 2011-12-21.
  11. ^ Yadron, Danny (9 July 2015). "Moxie Marlinspike: The Coder Who Encrypted Your Texts". The Wall Street Journal. Retrieved 10 July 2015.
  12. ^ Andy Greenberg (2011-11-28). "Twitter Acquires Moxie Marlinspike's Encryption Startup Whisper Systems". Forbes. Retrieved 2011-12-21.
  13. ^ Garling, Caleb (2011-11-28). "Twitter Buys Some Middle East Moxie | Wired Enterprise". Wired. Retrieved 2011-12-21.
  14. ^ Chris Aniszczyk (20 December 2011). "The Whispers Are True". The Twitter Developer Blog. Twitter. Archived from the original on 24 October 2014. Retrieved 22 January 2015.
  15. ^ "TextSecure is now Open Source!". Whisper Systems. 20 December 2011. Archived from the original on 6 January 2012. Retrieved 22 January 2015.
  16. ^ Pete Pachal (2011-12-20). "Twitter Takes TextSecure, Texting App for Dissidents, Open Source". Mashable. Retrieved 2014-03-01.
  17. ^ "RedPhone is now Open Source!". Whisper Systems. 18 July 2012. Archived from the original on 31 July 2012. Retrieved 22 January 2015.
  18. ^ a b Andy Greenberg (29 July 2014). "Your iPhone Can Finally Make Free, Encrypted Calls". Wired. Retrieved 18 January 2015.
  19. ^ a b "A New Home". Open Whisper Systems. 21 January 2013. Retrieved 23 January 2015.
  20. ^ a b Brian Donohue (Feb 24, 2014). "TextSecure Sheds SMS in Latest Version". Threatpost. Retrieved 2014-03-01.
  21. ^ Christine Corbett (27 March 2013). "Sure!". Open Whisper Systems. Retrieved 2014-03-16.
  22. ^ a b c d Moxie Marlinspike (24 February 2014). "The New TextSecure: Privacy Beyond SMS". Open Whisper Systems. Retrieved 26 February 2014.
  23. ^ "Free, Worldwide, Encrypted Phone Calls for iPhone". Open Whisper Systems. 29 July 2014.
  24. ^ Michael Mimoso (29 July 2014). "New Signal App Brings Encrypted Calling to iPhone". Threatpost.
  25. ^ Jon Evans (29 July 2014). "Talk Private To Me: Free, Worldwide, Encrypted Voice Calls With Signal For iPhone". TechCrunch. AOL.
  26. ^ Micah Lee (2015-03-02). "You Should Really Consider Installing Signal, an Encrypted Messaging App for iPhone". The Intercept. Retrieved 2015-03-03.
  27. ^ Megan Geuss (2015-03-03). "Now you can easily send (free!) encrypted messages between Android, iOS". Ars Technica. Retrieved 2015-03-03.
  28. ^ BastienLQ (20 April 2016). "Change the name of SMSSecure". GitHub (pull request). SilenceIM. Retrieved 27 September 2016.
  29. ^ "TextSecure-Fork bringt SMS-Verschlüsselung zurück". Heise (in German). 2 April 2015. Retrieved 29 July 2015.
  30. ^ "SMSSecure: TextSecure-Abspaltung belebt SMS-Verschlüsselung wieder". Der Standard (in German). 3 April 2015. Retrieved 1 August 2015.
  31. ^ a b c d Rottermanner et al. 2015, p. 5
  32. ^ a b Rottermanner et al. 2015, p. 9
  33. ^ DJ Pangburn (3 March 2014). "TextSecure Is the Easiest Encryption App To Use (So Far)". Motherboard. Archived from the original on 14 March 2014. Retrieved 14 March 2014.
  34. ^ a b Moxie Marlinspike (5 May 2014). "Private Group Messaging". Open Whisper Systems. Retrieved 2014-07-09.
  35. ^ a b "How can I get TextSecure working with my Google Voice number?". Open Whisper Systems. 6 March 2015. Archived from the original on 6 September 2015. Retrieved 2 January 2016.
  36. ^ a b Open Whisper Systems (18 March 2014). "Why do I need Google Play installed to use TextSecure on Android?". Archived from the original on 5 September 2015. Retrieved 2 January 2016.
  37. ^ "Moxie Marlinspike - 40 under 40". Fortune. Time Inc. 2016. Archived from the original on 3 February 2017. Retrieved 6 October 2016.
  38. ^ Unger et al. 2015, p. 241
  39. ^ a b Frosch et al. 2016
  40. ^ a b c d Unger et al. 2015, p. 239
  41. ^ Frosch et al. 2016, p. 7
  42. ^ a b c Rottermanner et al. 2015, p. 4
  43. ^ a b c Moxie Marlinspike (3 January 2013). "The Difficulty Of Private Contact Discovery". Open Whisper Systems. Retrieved 25 March 2014.
  44. ^ Rottermanner et al. 2015, p. 3
  45. ^ Andy Greenberg (2013-12-09). "Ten Million More Android Users' Text Messages Will Soon Be Encrypted By Default". Forbes. Retrieved 2014-02-28.
  46. ^ Seth Schoen (2013-12-28). "2013 in Review: Encrypting the Web Takes A Huge Leap Forward". Electronic Frontier Foundation. Retrieved 2014-03-01.
  47. ^ a b Moxie Marlinspike (2013-12-09). "TextSecure, Now With 10 Million More Users". Open Whisper Systems. Retrieved 2014-02-28.
  48. ^ Sinha, Robin (20 January 2016). "CyanogenMod to Shutter WhisperPush Messaging Service on February 1". Gadgets360. NDTV. Retrieved 4 March 2016.
  49. ^ Tom Ritter (14 Oct 2013). "Working with the Open Technology Fund". iSEC Partners. Retrieved 4 May 2015.
  50. ^ Pauli, Darren. "Auditors find encrypted chat client TextSecure is secure". The Register. Retrieved 4 November 2014.
  51. ^ Max Eddy (11 March 2014). "Snowden to SXSW: Here's How To Keep The NSA Out Of Your Stuff". PC Magazine: SecurityWatch. Retrieved 2014-03-16.
  52. ^ Hanno Böck (Mar 11, 2014). "Snowden empfiehlt Textsecure und Redphone" (in German). Golem.de. Retrieved 2014-03-16.
  53. ^ "The Virtual Interview: Edward Snowden - The New Yorker Festival". YouTube. The New Yorker. Oct 11, 2014. Retrieved May 24, 2015.
  54. ^ Alan Yuhas (May 21, 2015). "NSA surveillance powers on the brink as pressure mounts on Senate bill – as it happened". The Guardian. Retrieved May 24, 2015.
  55. ^ Zack Beauchamp (May 21, 2015). "The 9 best moments from Edward Snowden's Reddit Q&A". Vox Media. Retrieved May 24, 2015.
  56. ^ "Surveillance Self-Defense. Communicating with Others". Electronic Frontier Foundation. 2014-10-23.
  57. ^ a b c "Secure Messaging Scorecard. Which apps and tools actually keep your messages safe?". Electronic Frontier Foundation. 2014-11-04. Archived from the original on 2016-11-15. Retrieved 2014-11-08.
  58. ^ Stephanie Mlot (2014-11-18). "WhatsApp Rolling Out End-to-End Encryption". PC Magazine. Retrieved 2014-11-24.
  59. ^ Franceschi-Bicchierai, Lorenzo (18 November 2014). "WhatsApp messages now have Snowden-approved encryption on Android". Mashable. Retrieved 23 January 2015.
  60. ^ "Donate to Support Encryption Tools for Journalists". Freedom of the Press Foundation. Retrieved 17 October 2016.
  61. ^ "TextSecure". Knight Foundation. Retrieved 5 January 2015.
  62. ^ "Moxie Marlinspike". Shuttleworth Foundation. September 2013. Archived from the original on 18 January 2015. Retrieved 14 January 2015.
  63. ^ "Open Whisper Systems". Open Technology Fund. Retrieved 26 December 2015.


  • 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). 2016 IEEE European Symposium on Security and Privacy (EuroS&P). Saarbrücken, Germany: IEEE. pp. 457–472. CiteSeerX doi:10.1109/EuroSP.2016.41. ISBN 978-1-5090-1752-2.
  • 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 18 March 2016.
  • Unger, Nik; Dechand, Sergej; Bonneau, Joseph; Fahl, Sascha; Perl, Henning; Goldberg, Ian Avrum; Smith, Matthew (2015). "SoK: Secure Messaging" (PDF). 2015 IEEE Symposium on Security and Privacy. 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. ISBN 978-1-4673-6949-7.

External links[edit]