You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been using CMAC with AES-128, or AES-CMAC as specified in RFC 4493, with the help of a gem that targets that RFC.
In several months, I will need to use CMAC with more ciphers, which is outside the scope of such gems.
After looking for alternative implementations, I think it would be best to make OpenSSL's CMAC implementation available to Ruby code.
FWIW: Since CMAC is available through the EVP_PKEY API (see the man page EVP_PKEY-CMAC(7)), OpenSSL::PKey automatically supports it. However, with a limitation that the message must be given as a single String.
Activity
rhenium commentedon Oct 29, 2024
FWIW: Since CMAC is available through the
EVP_PKEYAPI (see the man pageEVP_PKEY-CMAC(7)),OpenSSL::PKeyautomatically supports it. However, with a limitation that the message must be given as a singleString.kmfukuda commentedon Nov 8, 2024
Thanks. I couldn't start using a feature that I knew was already considered legacy.