Nic

Ok I'll do what I can. I'm quite awake for some reason. And I just realised I read the assignment wrong, so ignore my last.

3.30am update: I can't sign the (name, top, length) tuples using RSA, I'm assuming to do with that length problem from before. Technically anything we send is AES encrypted anyway, so it's basically signed. I don't know if that's good enough though. This whole bank thing is stupid anyway. Text me when you get to uni tomorrow and I'll come join you.

Alex

I'm off to bed, will look at preventing replay when i get to uni early tomorrow probably

Alex

I'm storing files local to the server, the historically remembered login credentials of users
i.e. if a user logs in for the 2nd time the server checks that it is the same person
Currently those files are unencrypted, this may cause problems but is a 20 minute fix if need be (i'm ignoring it for now)
Clients do not try to remember each-other's public keys, they trust the server to provide them

Currently all chatting uses public key authentication via the server, will add to file-sending shortly

This is becoming a massive hack :)


Nic

Oops, sorry about that. I merged like 3 times before I actually pushed. Fun times.

For the report, I'm stealing your explanation of key exchange from last time. That's most of it written for me. Awesome.

Reading through the assignment I just noticed that we have to store files on the server. Are you doing that or should I?

PS: Until I get bored of it all of my commit messages are now song lyrics (inc the last two)