 Secure Chat Window
Stephen must now update the team with new orders. On the Messaging tab,
Stephen can see a conversation with an individual or group, much like the
standard chat application on his phone. In this case, his can message John Doe
securely because he has a public key stored for him. The application reminds him
that he can securely communicate via color (background color), and each past
message that was sent with encryption is also set off by color and a lock icon. Groups
can be handled similarly to individuals with a group key.
Touching on the message area to enter a message brings up the keyboard and a lock
button, giving access to encryption options for the message (encrypt via personal
private key or public key of John Doe). The default encrypts via public key to ensure
safety, but Stephen can remove this if he decides encryption is not necessary for a particular message.
. 
GR2-DesignsUnsecure Chat Window
This is the same view of the messaging window but for a contact without a stored
public key. The background color is red, reminding Stephen that no message can
be sent securely, and the lock icon near the message window is disabled.
| Pros: Mimics Conversation/Chat flow concepts.
Multiple signals for secure or unsecure communications
(lock icon near name, Lock on each securely sent/received
message, background color, message bubble color).
Cons: User must learn difference between using public or
private key.
| Pros: Streamlined interface for all secure and
unsecure communications with a single person or
group.
Default option uses secure public key encryption,
which requires user intervention if a different option
is desired (assumes this is the most likely selected
option).
Cons: Receiving a secure message
requires decryption using either personal private
or contact's public key, requiring extra time.
| Pros: Multiple visual cues to signify message security.
Cons: User can still send an unsecure message, so there
is still risk of secret information being sent unsecurely.
|