On 06/26/2013 07:18 PM, bassamtabbara wrote:
> In our case the old code prior to this change has already been
> released (in firmware) as well. Is there an easy way to get the
> version of cryptodev so that we can make the use of SHA_256
> conditional on the version?
Of course. You can modify th
On 06/26/2013 10:43 AM, bassamtabbara wrote:
> this line broke our code that relies on CRYPTO_SHA2_256 having a value of 103
> in the enum. It also breaks compatibility with older versions of this
> library. Can CRYPTO_SHA2_224 go at the bottom of the enum instead?
> https://github.com/nmav/cryp
