aboutsummaryrefslogtreecommitdiffstats
path: root/src/main/java/eu/siacs/conversations/ui/TrustKeysActivity.java (follow)
Commit message (Collapse)AuthorAgeFilesLines
* remove own fetch errors from device announcementDaniel Gultsch2016-12-161-2/+0
|
* allow fingerprint verification via context menuDaniel Gultsch2016-11-281-15/+12
|
* explictly scan for aztec and qr codes onlyDaniel Gultsch2016-11-231-1/+2
|
* introduced blind trust before verification modeDaniel Gultsch2016-11-231-4/+11
| | | | read more about the concept on https://gultsch.de/trust.html
* offer verification directly from the trust keys screenDaniel Gultsch2016-11-221-1/+72
|
* parse omemo fingerprints from urisDaniel Gultsch2016-11-171-1/+4
|
* refactor omemo fingerprint UI codeDaniel Gultsch2016-11-151-10/+6
|
* refactore trust enum to be FingerprintStatus class with trust and activeDaniel Gultsch2016-11-141-7/+8
|
* properly persist accepted crypto targetsDaniel Gultsch2016-03-011-5/+1
|
* let users confirm each member in a conference even if that contact is ↵Daniel Gultsch2016-03-011-15/+35
| | | | already trusted
* refactored omemo to take multiple recipientsDaniel Gultsch2016-02-291-68/+88
|
* show fetch errors in trust keys activityDaniel Gultsch2016-01-231-1/+2
|
* use extract account from intent method and final EXTRA_ACCOUNT variableDaniel Gultsch2016-01-221-1/+1
|
* show key fetch error in activity when there are no keys to be usedDaniel Gultsch2016-01-131-1/+8
|
* show certificate informationDaniel Gultsch2015-12-231-0/+2
|
* improved error reporting in trust keys activityDaniel Gultsch2015-10-171-10/+20
|
* introduced code to verify omemo device keys with x509 certificates.Daniel Gultsch2015-10-161-32/+48
| | | | cleaned up TrustKeysActivity to automatically close if there is nothing to do
* Only show that have sessions in fingerprint listAndreas Straub2015-09-061-18/+18
| | | | | | | | | Doesn't access database directly anymore but goes through AxolotlService now to obtain list of fingerprints associated with an Account/Contact. This should prevent orphaned keys littering the UI which previously couldn't be removed through the Clear Devices function. Together with 1c79982da84964c1d81179a0927d9cd1eadf53de this fixes #1393
* Display error message if all contact keys purgedAndreas Straub2015-08-151-0/+10
|
* renamed multi-end / axolotl to OMEMODaniel Gultsch2015-08-081-1/+1
|
* Improve TrustKeysActivity slider responsivenessAndreas Straub2015-08-051-11/+11
| | | | | | Slider used to skip back on drag-and-drop action. The switch doesn't trigger explicit whole UI refreshes anymore, it now directly adjusts the "done" button's locked status.
* Let UNTRUSTED/UNDECIDED keys become INACTIVEAndreas Straub2015-08-011-9/+9
|
* Highlight selected message's fingerprint in listAndreas Straub2015-07-291-2/+2
|
* Refactor out inner classes, cache trust storeAndreas Straub2015-07-291-1/+1
| | | | | | | Moves SQLiteAxolotlStore and XmppAxolotlSession into proper classes. IdentityKeys trust statuses are now cached in an LruCache to prevent hammering the database when rendering the UI.
* Add INACTIVE state for removed keysAndreas Straub2015-07-211-3/+3
| | | | | | | | | | | | | We introduce a new trust state: INACTIVE. This state is intended for old keys that have been removed. When a TRUSTED device is removed from the PEP devicelist, it's status will be set to INACTIVE. INACTIVE keys are shown in the UI as greyed out, non-interactible key rows. Messages are not encrypted for INACTIVE devices. When an INACTIVE device reappears in PEP, or a message is received from an INACTIVE device, it is set back to trusted.
* Start TrustKeysActivity if no keys are TRUSTEDAndreas Straub2015-07-201-2/+8
| | | | | If there are no UNDECIDED keys, but none of the contact's keys are trusted, redirect the user to the TrustKeysActivity
* rely on refreshUi/refreshUiReal and make sure it is being used everywhereDaniel Gultsch2015-07-201-10/+4
|
* Lock TrustKeys if no trusted keys are availableCryptoNextBetaAndreas Straub2015-07-201-4/+26
|
* Optimize importsAndreas Straub2015-07-201-4/+0
|
* Ask for key trust when sending messagesAndreas Straub2015-07-191-0/+237
If the contact (or the own account) has keys that have UNDECIDED trust, we now drop the user into the new TrustKeysActivity, where they have to decide for each new key whether it should be TRUSTED or UNTRUSTED.