LOC-10 - Use server-validated username to define message sender
author B Tasker
()
committer B Tasker
()
commit d12630afc3930ef9814a8d464fe7fe81ecaf3997
tree 7cb04354c9e20577db8850d07d5aa8ffbb3c4a5f
parent 2c0106df1c185ca2add6e2b1d9261e0cbdd9cb54
LOC-10 - Use server-validated username to define message sender

We now use the username field that's authenticated by the server when displaying who the sender was. The "user" field has been removed from the encrypted message payload as being potentially dangerous (and no longer used in any case).

This means that it should no longer be possible to spoof the sender of messages. Instead you'd need to compromise an existing user's session or password.

The trade off of this is that there's a slightly increased level of metadata in memory on the server, but having weighed the options in LOC-10 this was deemed lower risk than the alternative.
client/LocalChatClient.py
server/LocalChat.py