Secure SaverServer communications using SSL rather than raw AES

[twa16]

Some strange demon possessed me when i was writing the first version prototype and I used raw AES to secure communications. I reinvented the wheel.... So we should use SSL to secure streams. This will be a rather involved process since I used the packets for user identification since a user without valid credentials would be unable to communicate with the server properly.

Steps:

1. Separate auth from protocol crypto
2. Move from raw aes to ssl for communication