Off-the-Record Messaging

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Off-the-Record Messaging, commonly referred to as OTR, is a cryptographic protocol that provides strong encryption for instant messaging conversations. OTR uses a combination of the AES symmetric-key algorithm, the Diffie–Hellman key exchange, and the SHA-1 hash function. In addition to authentication and encryption, OTR provides perfect forward secrecy and malleable encryption.

The primary motivation behind the protocol was providing deniability for the conversation participants while keeping conversations confidential, like a private conversation in real life, or off the record in journalism sourcing. This is in contrast with other cryptography tools that produce output which can be later used as a verifiable record of the communication event and the identities of the participants. In most cases, people using such cryptography software are not aware of this and might be better served by OTR tools instead.[citation needed] The initial introductory paper was named "Off-the-Record Communication, or, Why Not To Use PGP".[1]

The OTR protocol was designed by cryptographers Ian Goldberg and Nikita Borisov. They provide a client library to facilitate support for instant messaging client developers who want to implement the protocol. A Pidgin and Kopete plugin exists that allows OTR to be used over any IM protocol supported by Pidgin or Kopete, offering an auto-detection feature that starts the OTR session with the buddies that have it enabled, without interfering with regular, unencrypted conversations.

Implementation[edit]

In addition to providing encryption and authentication — features also provided by typical public-key cryptography suites, such as PGP, GnuPG, and X.509 (S/MIME) — OTR also offers some less common features:

  • Perfect forward secrecy: Messages are only encrypted with temporary per-message AES keys, negotiated using the Diffie-Hellman key exchange protocol. The compromise of any long-lived cryptographic keys does not compromise any previous conversations, even if an attacker is in possession of ciphertexts.
  • Deniable authentication: Messages in a conversation do not have digital signatures, and after a conversation is complete, anyone is able to forge a message to appear to have come from one of the participants in the conversation, assuring that it is impossible to prove that a specific message came from a specific person. Within the conversation the recipient can be sure that a message is coming from the person they have identified.

Authentication[edit]

As of OTR 3.1, the protocol supports mutual authentication of users using a shared secret through the socialist millionaire protocol. This feature makes it possible for users to verify the identity of the remote party and avoid a man-in-the-middle attack without the inconvenience of manually comparing public key fingerprints through an outside channel.

Limitations[edit]

Due to limitations of the protocol, OTR does not support multi-user group chat as of 2009[2] but may be implemented in the future. As of version 3[3] of the protocol specification, an extra symmetric key is derived during authenticated key exchanges that can be used for secure communication (e.g., encrypted file transfers) over a different channel. Support for encrypted audio or video is not planned. (SRTP with ZRTP exists for that purpose.)

Since OTR protocol v3 (pidgin-otr 4.0.0 and libotr 4.0.0) the plugin supports multiple OTR conversations with the same buddy who is logged in at multiple locations.[4]

Client support[edit]

Native[edit]

These clients support Off-the-Record Messaging out of the box.

Via plug-in[edit]

Off-The-Record authentication in Pidgin using Socialist millionaires protocol

The following clients require a plug-in to use Off-the-Record Messaging.

Google talk[edit]

Although Gmail's Google Talk uses the term "off the record", the feature has no connection to the Off-the-Record Messaging protocol described in this article, its chats are not encrypted in the way described above - and could be logged internally by Google even if not accessible by end-users.[21][22]

References[edit]

  1. ^ Nikita Borisov, Ian Goldberg, Eric Brewer (2004-10-28). "Off-the-Record Communication, or, Why Not To Use PGP" (PDF). Workshop on Privacy in the Electronic Society. Retrieved 2014-03-06. 
  2. ^ Ian Goldberg (May 27, 2009). "multi-party OTR communications? (and other OTR details)". OTR-users mailing list. 
  3. ^ "Off-the-Record Messaging Protocol version 3". 
  4. ^ Ian Goldberg (September 4, 2012). "pidgin-otr and libotr 4.0.0 released!". OTR-announce mailing list. 
  5. ^ "BitlBee Wiki". Wiki.bitlbee.org. 2014-01-25. Retrieved 2014-05-15. 
  6. ^ "kopete-otr in KDE for 4.1". 
  7. ^ "kopete-otr review request". 
  8. ^ 0xd34df00d. "OTR Plugin". Github.com. Retrieved 2014-05-15. 
  9. ^ "Short description". Leechcraft.org. Retrieved 2014-05-15. 
  10. ^ "source code". Mcabber.com. 2013-10-25. Retrieved 2014-05-15. 
  11. ^ "OTR Plugin". Github.com. Retrieved 2014-05-15. 
  12. ^ "Psi+ snapshots". Github.com. Retrieved 2014-05-15. 
  13. ^ "OTR plugin for Gajim". 
  14. ^ "Gajim Wiki". 
  15. ^ "irssi-otr / xchat-otr plugin". 
  16. ^ "Miranda OTR Plugin". 
  17. ^ "OTR plugin for pidgin". 
  18. ^ "Psi-Patches and OTR-Plugin on". Tfh-berlin.de. Retrieved 2014-05-15. 
  19. ^ "Tkabber OTR Plugin". 
  20. ^ "OTR plugin for WeeChat". 
  21. ^ "Chatting off the record - Talk Help". 
  22. ^ "Google Talk - Privacy Policy". 

Further reading[edit]

External links[edit]