aboutsummaryrefslogtreecommitdiffstats
path: root/src/main/java/eu/siacs/conversations/ui/TrustKeysActivity.java (unfollow)
Commit message (Collapse)AuthorFilesLines
2015-08-15Display error message if all contact keys purgedAndreas Straub1-0/+10
2015-08-08renamed multi-end / axolotl to OMEMODaniel Gultsch1-1/+1
2015-08-05Improve TrustKeysActivity slider responsivenessAndreas Straub1-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.
2015-08-01Let UNTRUSTED/UNDECIDED keys become INACTIVEAndreas Straub1-9/+9
2015-07-29Highlight selected message's fingerprint in listAndreas Straub1-2/+2
2015-07-29Refactor out inner classes, cache trust storeAndreas Straub1-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.
2015-07-21Add INACTIVE state for removed keysAndreas Straub1-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.
2015-07-20Start TrustKeysActivity if no keys are TRUSTEDAndreas Straub1-2/+8
If there are no UNDECIDED keys, but none of the contact's keys are trusted, redirect the user to the TrustKeysActivity
2015-07-20rely on refreshUi/refreshUiReal and make sure it is being used everywhereDaniel Gultsch1-10/+4
2015-07-20Lock TrustKeys if no trusted keys are availableAndreas Straub1-4/+26
2015-07-20Optimize importsAndreas Straub1-4/+0
2015-07-19Ask for key trust when sending messagesAndreas Straub1-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.