> Should the caller specify an empty ivec (to the correct length) in this case
> or am I missing something?
I think so too.
If you always initialise the IVEC to NUL bytes,
and use the same key to encrypt lots of small packets,
it becomes easier to crack the key.
If you use some variable data tha
Sounds like a good idea, but a lot of work.
It also might need a discussion area (layer)
where people thrash it out before some volunteer
edits it over to the main area (and people comment again?)
I have some questions but not answers,
and would be happy to work on them one at a time.
I would expe
google: TCP OPTION KEEPALIVE
http://tldp.org/HOWTO/html_single/TCP-Keepalive-HOWTO/
You would be best with an application level timeout,
which would send an application enquiry (heartbeat)
from the laptop to the server.
Waking up from sleeping, the application would send the next heartbeat.
(any
With EVP/AES I cannot change encrypt/decrypt after setting KEY
bool ok = EVP_CipherInit_ex( &ctx, type, impl, key, iv, enc );
I am calling EVP_CipherInit_ex() more than once.
I set the key early then later set enc (or change it after a default CTOR).
The DOCS says simply leave things NULL for the
