AES is a symmetric (1 key) algorithm, so the recipient must use the original key to verify the HMAC.
If you use AES to make a signature, you have to get the original key to your recipient and trust (s)he doesn't share it. So you can't really use symmetric algorithms to authenticate your messages if your target is the general public because you'd have to share your key with everyone (and a bad actor could turn around and imitate you). This is why we use asymmetric algorithms for digital signatures. !!Dean KC4KSU On Aug 27, 2016, at 8:29 PM, Steve wrote: > Dean, the AES STM32 library does have three HMAC (one-way) hash > algorithms built-in. Four if you count MD5, but no one counts that > anymore :-) > > 73/steve > > ------------------------------------------------------------------------------ > _______________________________________________ > Freetel-codec2 mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 ------------------------------------------------------------------------------ _______________________________________________ Freetel-codec2 mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freetel-codec2
