sum7/Conversations
sum7
/
Conversations
1
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity

updated changelog and readme for the 0.3 release

This commit is contained in:
iNPUTmice 2014-06-01 19:48:44 +02:00
parent 1982151630
commit f94254de16
2 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
CHANGELOG.md
View File

@ -1,5 +1,11 @@
###Changelog ###Changelog
####Version 0.3
* Mostly bug fixes and internal rewrites
* made OTR more reliable
* improved issues with occasional message lost
* experimental conference encryption. (see FAQ)
####Version 0.2.3 ####Version 0.2.3
* regression fix with receiving encrypted images * regression fix with receiving encrypted images

14
README.md
View File

@ -44,6 +44,7 @@ These XEPs are - as of now:
###Code ###Code
* [Rene Treffer](https://github.com/rtreffer) * [Rene Treffer](https://github.com/rtreffer)
* [Andreas Straub](https://github.com/strb) * [Andreas Straub](https://github.com/strb)
* [Alethea Butler](https://github.com/alethea)
###Translations ###Translations
* [Sergio Cárdenas](https://github.com/kruks23) (Spanish) * [Sergio Cárdenas](https://github.com/kruks23) (Spanish)
@ -100,6 +101,19 @@ 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 attacks, it is rather verbose, and 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. 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 ###Development
####How do I build Conversations ####How do I build Conversations
Make sure to have ANDROID_HOME point to your Android SDK Make sure to have ANDROID_HOME point to your Android SDK