E2ee dev

[Sim0xx001]

I've implemented a few methods in e2ee.py for keys load from bytes strings and encrypting/decrypting messages.

[TheRealGioviok]

Couple things:

• I feel like the Cipher and E2EE classes are both prone to be used one over eachother, maybe by making the E2EE class static, since it really never does anything with self that couldn't be done by cipher.
• Maybe we could remove the start and end key strings to save space (when storing to disk).

In fact, I think that the system should be modified as follows:

• The Identity class (former Cipher) should be able storing both public and private keys. It should also provide the two methods to cipher and decipher, maybe returning error values if we try to decode using an Identity which is associated with only the public key. It should be the only class directly used in both server and client code.
• The E2EE class should be a static class that provides utility functions to be only used under-the-hood by the Identity class, such as loading/storing keys from disk/bytes.
• Of course, these modifications would require some changes to other files.

As for the Message.py, me and Bruno are working on a simpler protocol with only two classes, Packet and PacketItem. Just remove all the message classes and leave the send/receive methods. You may consider moving the two functions to the new E2EE.py, so that you can delete the message.py file altogheter.

If these things above-mentioned are done, I think we will be ready for merge.

[Sim0xx001]

All done!

[TheRealGioviok]

Reopening your pull request... :)

[TheRealGioviok]

Merging.