Let's say I'm developing a library for signing / verifying messages using the SHA-256 HMAC. If the end user uses a weak public key and sends a lot of short messages, I assume that the key is at risk for the attacker.
My intuition says that I have to add a unique salt (for each message) to the key in order to make reverse development key more difficult.
How much would the key help me, and could I get anything while also stuffing messages?
source share