EVP_MAC_init() in 3.0 alpha 13

[Hal Murray]

tomas at openssl.org said:
> We would have to introduce the special semantics similar to EVP_CipherInit()
> with EVP_MAC_init(). I.e., that the EVP_CipherInit() with NULL key keeps the
> key schedule from the previous initialization. 

Seems like a good idea to me.  The current code doesn't crash and doesn't 
generate an error return.  Is there any other useful thing that a NULL key 
could do?

I don't have a big picture view.  Is there any reason that all of the crypto 
init type procedures can't keep the current key schedule if called with a NULL 
key?

Am I the only one (so far) that is interested in reusing the current key 
schedule to save CPU cycles?



-- 
These are my opinions.  I hate spam.