Key Management
Stephen must add the new teammates to his list of secure contacts. The SecureConnect application allows him to log onto the Key Server set up by the campaign to manage public keys. He finds that two of the new volunteers had public keys created for them when issued their mobile phones, so he adds them to his personal contact list, which include their mobile phone number and public key. One user was not yet present in the key server, so Stephen had to help generate a new key for them.
This design is meant to mimic a standard phone text messaging layout which the user is likely familiar with, then overlaying the metaphor of user keys necessary to facilitate encrypted messaging.
| Pros:
Cons:
| Pros:
Cons: | Pros:
Cons: |
![](/confluence/download/attachments/82324422/photo1.jpg?version=1&modificationDate=1331520390000&api=v2)
photo1.jpg Contact Management Once the new contacts were added from the Key Server, Stephen is able to view them the contacts tab of the app. Each newly added secure contact with a stored public key is displayed with a key icon next to their name at all times. Contacts without a stored key are also present, and can have a public key entered on the contact editor in order to make them a secure contact.
Public keys can be entered manually via the keyboard, pasted from the phone's clipboard (the contact could have sent their key via email or unsecure text, or could have been located via web browser).
| Pros:
Cons: | Pros:
Cons: | Pros:
Cons: |