Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Add INACTIVE state for removed keys | Andreas Straub | 2015-07-21 | 1 | -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 TRUSTED | Andreas Straub | 2015-07-20 | 1 | -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 everywhere | Daniel Gultsch | 2015-07-20 | 1 | -10/+4 |
| | |||||
* | Lock TrustKeys if no trusted keys are available | Andreas Straub | 2015-07-20 | 1 | -4/+26 |
| | |||||
* | Optimize imports | Andreas Straub | 2015-07-20 | 1 | -4/+0 |
| | |||||
* | Ask for key trust when sending messages | Andreas Straub | 2015-07-19 | 1 | -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. |