Skip to content

Latest commit

 

History

History
108 lines (103 loc) · 6.03 KB

contribute.md

File metadata and controls

108 lines (103 loc) · 6.03 KB
Raw
layout title tags permalink
page
Contribute
menu
/contribute/

How to contribute


This section should guide you through the initial steps of contributing to OTR. Thank you! Welcome, we're delighted to see you! :)

If you have any questions, comments, doubts or concerns, please, feel free to reach us at the #otr channel on the OFTC IRC network. We also have an slack channel for more contact. You can also contact us through our mailing list.

For requests, suggestions and bug reports, please open an issue on our Gitlab, on the appropriate repository. If you want to fix a bug or suggest something, ask for mentoring to Sofía Celi at [email protected]

A few things anyone can do

  • Spread the word around OTR and its new version. Tell your friends!
  • We always look for examples of how OTR is used or how or how can it be used. If you know, let us know!

More contact points


Our contact points are listed on the lovely footer; but we have more:

  • User mailing list: OTR has numerous users from all kinds of backgrounds, next to it being used by several hundred-thousands throughout the the world. Signup to the user mailinglist to help us improve its usability!
  • Announce mailinglist: If you're interested in being notified when new releases are put out or want to follow the latest news. Please subscribe to the otr-announce mailinglist!

Sponsorship


OTR (in its version 4) is sponsored by the NLNet Foundation. Funding was provided through the NGI0 Privacy Enhancing Technologies Fund, a fund established by NLnet with financial support from the European Commission’s Next Generation Internet program, under the aegis of DG Communications Networks, Content and Technology under grant agreement #825310.

Our own jabber service

OTR.im chat

OTR.im offers a free and secure Jabber service that anyone can use by registering an account through your favorite chat client.

➛ jabber.otr.im

It is also possible to connect to it through our Tor hidden service:

➛ 5rgdtlawqkcplz75.onion

In order to configure a Jabber client, you need this information:

Protocol: jabber or xmpp

Account: [email protected]

Our Jabber server requires a secure SSL/TLS connection. We use Let's Encrypt since March 22nd, 2016 thus you should expect a valid signed certificate for jabber.otr.im.

Finally, this server has a special quirk. It forces communication to be OTR encrypted, thus cleartext messages between clients is impossible. With the help of Riseup, we have developed a prosody plugin to achieve mandatory OTR communication.

Data Retention

What data does OTR.im can see and can not see with this Jabber server:

First of all, this server is setup with full disk encryption (FDE) so all that we store is only on an encrypted disk. We use a LUKS device for this. Secondly, logging is completely disabled on the Jabber server, even error logs.

In case of a seizure, if the server is powered off, the FDE will protect all data. If the server is kept online, see the 'What we can see?' section below.

What we CAN see?

  • Your username and SHA1 hash of the password are stored on the server.
  • vCard if you supply one.
  • Your IP address. To avoid this, use our Tor hidden service.
  • Offline messages. Any messages you send to an offline contact will be stored encrypted on the server until the contact shows up:
    • Encrypted content with OTR.
    • Destination contact address.
    • Timestamp of the messages sent.
  • Your roster. For each contact, we see:
    • Jabber address (for example: [email protected])
    • Name of the contact (if set)
    • Group it belongs to (if any)

<h2>What we DO NOT see?</h2>
<ul>
  <li>The Message content. Mandatory OTR makes it that we can't read content of your messages.</li>
  <li>No logs, except for what our prosody server usually tell us.</li>
  <li>We don't keep any timing metadata such as when you connect or disconnect.</li>
</ul>