Thanks.
> and a CMAC key using the function EVP_PKEY_new_CMAC_key():
That's the step I was missing. Right in front of my eyes.
I'm still missing something though.
Does this look reasonable:
cipher = EVP_aes_128_cbc();
pkey = EVP_PKEY_new_CMAC_key(NULL, key, keylength, cipher);
ctx
On 12/06/2020 00:27, Hal Murray wrote:
>
> levi...@openssl.org said:
>> In 1.1.1 and earlier, there is a different idea, using EVP_PKEY routines to
>> "sign" with a MAC. We have a EVP_PKEY to EVP_MAC bridge in 3.0.0 to bridge
>> the gap.
>
> Thanks, but...
>
> The EVP_PKEY seems to assume a
levi...@openssl.org said:
> In 1.1.1 and earlier, there is a different idea, using EVP_PKEY routines to
> "sign" with a MAC. We have a EVP_PKEY to EVP_MAC bridge in 3.0.0 to bridge
> the gap.
Thanks, but...
The EVP_PKEY seems to assume a public/private key environment. The man page
for EVP_
On Thu, 11 Jun 2020 02:49:04 +0200,
Hal Murray wrote:
> CMAC_* have been DEPRECATED for 3.0.0
>
> CHANGES.md suggests using EVP_MAC_xxx. Mostly, that seems reasonable, but
> there is one loose end.
>
> CMAC_Init includes a key and cipher. What's the equivalent in EVP_MAC_xxx?
>
> ---
CMAC_* have been DEPRECATED for 3.0.0
CHANGES.md suggests using EVP_MAC_xxx. Mostly, that seems reasonable, but
there is one loose end.
CMAC_Init includes a key and cipher. What's the equivalent in EVP_MAC_xxx?
---
I found the params stuff, but that's new in 3.0.0
How do I do it in
