diff options
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 27 |
1 files changed, 22 insertions, 5 deletions
@@ -42,11 +42,15 @@ These XEPs are - as of now: (In order of appearance) ###Code -* Rene Treffer @rtreffer -* Andreas Straub @strb +* [Rene Treffer](https://github.com/rtreffer) +* [Andreas Straub](https://github.com/strb) +* [Alethea Butler](https://github.com/alethea) ###Translations -* @beriain (Spanish and Basque) +* [Sergio Cárdenas](https://github.com/kruks23) (Spanish) +* [Benoit Bouvarel](https://github.com/BenoitBouvarel) (French) +* [Daniel Gultsch](https://github.com/iNPUTmice) (German) +* [Aitor Beriain](https://github.com/beriain) (Basque) ##FAQ ###General @@ -86,7 +90,7 @@ not supported for simplicity reasons. Users tend to forget their status, other users ignore them and setting the status automatically would mean too much of an impact on privacy. ###Security -####Why are there to end-to-end encryption methods and which one should I choose? +####Why are there two end-to-end encryption methods and which one should I choose? In most cases OTR should be the encryption method of choice. It works out of the box with most contacts as long as they are online. However PGP can be in some cases (carbonated messages to multiple clients) be more flexible. @@ -94,9 +98,22 @@ more flexible. Before you continue reading you should notice that the openPGP support in Conversations is marked as experimental. This is not because it will make the app unstable but because the fundamental concepts of PGP aren't ready for a -widespread use. The way PGP works is that you trust Key IDs instead of XMPP- or email addresses. So in theory your contact list should consist of Public-Key-IDs instead of email addresses. But of course no email or xmpp client out there implements these concepts. Plus PGP in the context of instant messaging has a couple of downsides. It is vulnerable to replay attacs, it is rather verbose, decryping and encrypting takes longer than OTR. It is however asynchronous and works well with carbonated messages. +widespread use. The way PGP works is that you trust Key IDs instead of XMPP- or email addresses. So in theory your contact list should consist of Public-Key-IDs instead of email addresses. But of course no email or xmpp client out there implements these concepts. Plus PGP in the context of instant messaging has a couple of downsides. It is vulnerable to replay attacks, it is rather verbose, and decryping and encrypting takes longer than OTR. It is however asynchronous and works well with carbonated messages. To use openpgp you have to install the opensource app OpenKeychain (www.openkeychain.org) and then long press on the account in manage accounts and choose renew PGP announcement from the contextual menu. +####How does the encryption for conferences work? +For conferences the only supported encryption method is OpenPGP. (OTR does not +work with multiple participents.) Every participant has to announce their +OpenPGP key. (See answer above). If you would like to send encrypted messages to +a conference you have to make sure that you have every participants public key +in your OpenKeychain. Right now there is no check in Conversations to ensure +that. You have to take care of that yourself. Go to the conference details and +touch every key id (The hexadecimal number below a contact). This will send you +to OpenKeychain which will assist you on adding the key. +This works best in very small conferences with contacts you are already using +OpenPGP with. This feature is regarded experimental. Conversations is the only +client that uses XEP-0027 with confercenes. (The XEP neither specifically allows +nor disallows this.) ###Development ####How do I build Conversations Make sure to have ANDROID_HOME point to your Android SDK |