luigix25 / sslp Goto Github PK

This happens both in client and in server ONLY when terminating the process using SIGINT ( ctrl c )
If both client or server, terminate without being forced, no memory is still reachable.

The number of bytes ( around 60k for verify, 300 for sign ) is costant no matter how many times RSA functions are called.

It may be possible due to OpenSSL library lazy deallocation of memory

Right now whenever a client closes the connection, the server shuts down

Check the example here:
http://www.cplusplus.com/reference/istream/basic_istream/read/

The server can have just one connection with client at time, but it should have more clients available for communication.
So we need to authenticate the client through:
-a password
-a certificate

if we use the last one, then we need to to save a client list, since whenever we have to check the validity of a certificate, we also need to be sure that the subject of the certificate is in the list of our client list.

We can have a client list in server that we can manually change it.

if we go through this way, we need to add in the specification file that registration doesn't exist, but the server should manually add the client in the client list to allow him to access the shared database.

Compute HMAC on integer with nonce in order to guarantee replay and integrity