Re: [EXTERNAL] Re: what is a replacement for private_AES_set_encrypt_key and AES_encrypt functions

2018-03-13 Thread Vitaly Andrianov
On 03/12/2018 10:43 AM, Ard Biesheuvel wrote: On 12 March 2018 at 14:38, Vitaly Andrianov wrote: Hello, The Texas Instruments keystone2 out-of-tree kernel uses the private_AES_set_encrypt_key() and the AES_encrypt() at the crypto HW acceleration driver. The "crypto: arm/aes -

Re: what is a replacement for private_AES_set_encrypt_key and AES_encrypt functions

2018-03-12 Thread Ard Biesheuvel
On 12 March 2018 at 14:38, Vitaly Andrianov wrote: > Hello, > > The Texas Instruments keystone2 out-of-tree kernel uses the > private_AES_set_encrypt_key() and > the AES_encrypt() at the crypto HW acceleration driver. > > The "crypto: arm/aes - replace bit-sliced OpenSSL NEON

what is a replacement for private_AES_set_encrypt_key and AES_encrypt functions

2018-03-12 Thread Vitaly Andrianov
Hello, The Texas Instruments keystone2 out-of-tree kernel uses the private_AES_set_encrypt_key() and the AES_encrypt() at the crypto HW acceleration driver. The "crypto: arm/aes - replace bit-sliced OpenSSL NEON code" commit removed those functions. Here is a code, which calls the removed