[erlang-questions] Problem with legacy code when upgrading to R16B03
Wed Feb 18 00:27:26 CET 2015
Thank you Felix. It looks like the aes_cbc_128_encrypt method is gone so I
changed all to use crypto:block_encrypt(aes_cbc128, Key, IV, ToBeEncrypted)
But alas, I'm still seeing the same error.
On Tue, Feb 17, 2015 at 3:10 PM, Felix Gallo <felixgallo@REDACTED> wrote:
> I'm not super familiar with the crypto library, but it looks like its
> function signatures changed significantly between 15B01 and 16B03. In
> particular, it appears that some of the functions you are calling are no
> longer in the library, and have been replaced with equivalents.
> I suggest opening
> and seeing if you can figure out where the changes occurred. I suspect
> those are the cause of your badargs.
> On Tue, Feb 17, 2015 at 1:55 PM, Ryan Brown <ryankbrown@REDACTED> wrote:
>> Hello all,
>> I am in the process of upgrading a legacy application from R15B01 to
>> R16B03 in order to get SHA 384 support. However, I am getting an error
>> creating my CMAC from the library located here:
>> For the life of me I cannot find the root cause. I am just receiving a
>> badarg error pointing to line 74.
>> Any guidance would be greatly appreciated.
>> Thank you.
>> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions