Hi Horia,
On Fri, Apr 13, 2018 at 3:18 AM, Horia Geantă wrote:
> Stripping should happen before set_rsa_pub_pdb() is called since the Protocol
> Data Block contains the input length that is used by the accelerator:
> pdb->f_len = req->src_len;
>
> It should probably be moved at the top o
On 4/13/2018 3:12 AM, Fabio Estevam wrote:
> Hi Horia,
>
> On Thu, Apr 12, 2018 at 4:12 AM, Horia Geantă wrote:
>
>> Yes, driver needs to strip off leading zeros from input data before feeding
>> it
>> to the accelerator.
>> I am working at a fix.
>
> I was able to to strip off the leading zer
Hi Horia,
On Thu, Apr 12, 2018 at 4:12 AM, Horia Geantă wrote:
> Yes, driver needs to strip off leading zeros from input data before feeding it
> to the accelerator.
> I am working at a fix.
I was able to to strip off the leading zeros from input data as you suggested.
My changes are like this
On 4/11/2018 8:26 PM, Fabio Estevam wrote:
> Hi Horia,
>
> On Wed, Apr 11, 2018 at 7:15 AM, Horia Geantă wrote:
>
>> You'd want to make sure rsa is offloaded to caam in this case - check in
>> /proc/crypto.
>> IIRC there are some i.mx parts that don't have support for Public Key
>> acceleration
Hi Horia,
On Wed, Apr 11, 2018 at 7:15 AM, Horia Geantă wrote:
> You'd want to make sure rsa is offloaded to caam in this case - check in
> /proc/crypto.
> IIRC there are some i.mx parts that don't have support for Public Key
> acceleration (PKHA).
PKHA is present on mx6ul and not present on mx
On Wed, Apr 11, 2018 at 11:58 AM, Horia Geantă wrote:
> On 4/11/2018 1:36 AM, James Bottomley wrote:
>> On Tue, 2018-04-10 at 23:01 +0100, Martin Townsend wrote:
>>> Using openssl to get the signature in my x509 cert
>>>
>>>Signature Algorithm: sha256WithRSAEncryption
>>> 68:82:cc:5d:
Hi James,
On Tue, Apr 10, 2018 at 11:36 PM, James Bottomley
wrote:
> On Tue, 2018-04-10 at 23:01 +0100, Martin Townsend wrote:
>> Using openssl to get the signature in my x509 cert
>>
>>Signature Algorithm: sha256WithRSAEncryption
>> 68:82:cc:5d:f9:ee:fb:1a:77:72:a6:a9:c6:4c:cc:d7:f6
On 4/11/2018 1:36 AM, James Bottomley wrote:
> On Tue, 2018-04-10 at 23:01 +0100, Martin Townsend wrote:
>> Using openssl to get the signature in my x509 cert
>>
>> Signature Algorithm: sha256WithRSAEncryption
>> 68:82:cc:5d:f9:ee:fb:1a:77:72:a6:a9:c6:4c:cc:d7:f6:2a:
>> 17:a5:d
On 4/11/2018 5:21 AM, Fabio Estevam wrote:
> Hi Martin,
>
> On Tue, Apr 10, 2018 at 7:01 PM, Martin Townsend
> wrote:
>
>> A hexdump of the signature reveals a 0x00 at the start
>
> Yes, same is happening here on my mx6ul evk running linux-next:
>
[snip]
>
> However, the same kernel running o
Hi Martin,
On Tue, Apr 10, 2018 at 7:01 PM, Martin Townsend
wrote:
> A hexdump of the signature reveals a 0x00 at the start
Yes, same is happening here on my mx6ul evk running linux-next:
[2.990651] cfg80211: Loading compiled-in X.509 certificates for
regulatory database
[2.999046] sig
On Tue, 2018-04-10 at 23:01 +0100, Martin Townsend wrote:
> Using openssl to get the signature in my x509 cert
>
> Signature Algorithm: sha256WithRSAEncryption
> 68:82:cc:5d:f9:ee:fb:1a:77:72:a6:a9:c6:4c:cc:d7:f6:2a:
> 17:a5:db:bf:5a:2b:8d:39:60:dc:a0:93:39:45:0f:bc:a7:e8:
>
On Tue, Apr 10, 2018 at 7:43 PM, Martin Townsend
wrote:
> Hi Fabio,
>
> On Tue, Apr 10, 2018 at 7:22 PM, Fabio Estevam wrote:
>> Hi Martin,
>>
>> On Tue, Apr 10, 2018 at 2:06 PM, Martin Townsend
>> wrote:
>>> Hi Fabio,
>>>
>>> On Tue, Apr 10, 2018 at 5:59 PM, Fabio Estevam wrote:
Hi Martin
Hi Fabio,
On Tue, Apr 10, 2018 at 7:22 PM, Fabio Estevam wrote:
> Hi Martin,
>
> On Tue, Apr 10, 2018 at 2:06 PM, Martin Townsend
> wrote:
>> Hi Fabio,
>>
>> On Tue, Apr 10, 2018 at 5:59 PM, Fabio Estevam wrote:
>>> Hi Martin,
>>>
>>> On Mon, Apr 9, 2018 at 5:41 AM, Martin Townsend
>>> wrote:
Hi Martin,
On Tue, Apr 10, 2018 at 2:06 PM, Martin Townsend
wrote:
> Hi Fabio,
>
> On Tue, Apr 10, 2018 at 5:59 PM, Fabio Estevam wrote:
>> Hi Martin,
>>
>> On Mon, Apr 9, 2018 at 5:41 AM, Martin Townsend
>> wrote:
>>> Hi,
>>>
>>> I'm trying to get to the bottom of an issue I'm seeing when ena
Hi Fabio,
On Tue, Apr 10, 2018 at 5:59 PM, Fabio Estevam wrote:
> Hi Martin,
>
> On Mon, Apr 9, 2018 at 5:41 AM, Martin Townsend
> wrote:
>> Hi,
>>
>> I'm trying to get to the bottom of an issue I'm seeing when enabling
>> the CAAM in the kernel with IMA/EVM enabled. I'm using the official
>>
Hi Martin,
On Mon, Apr 9, 2018 at 5:41 AM, Martin Townsend wrote:
> Hi,
>
> I'm trying to get to the bottom of an issue I'm seeing when enabling
> the CAAM in the kernel with IMA/EVM enabled. I'm using the official
> NXP (imx_4.9.11_1.0.0_ga) vendor Kernel.
Does it work better if you try mainli
Hi Mike,
On Mon, Apr 9, 2018 at 5:53 PM, Mike Rapoport wrote:
> (added CAAM maintainers)
>
> On Mon, Apr 09, 2018 at 03:10:11PM +0100, Martin Townsend wrote:
>> Hi Mimi,
>>
>> On Mon, Apr 9, 2018 at 1:46 PM, Mimi Zohar wrote:
>> > On Mon, 2018-04-09 at 09:41 +0100, Martin Townsend wrote:
>> >> H
(added CAAM maintainers)
On Mon, Apr 09, 2018 at 03:10:11PM +0100, Martin Townsend wrote:
> Hi Mimi,
>
> On Mon, Apr 9, 2018 at 1:46 PM, Mimi Zohar wrote:
> > On Mon, 2018-04-09 at 09:41 +0100, Martin Townsend wrote:
> >> Hi,
> >>
> >> I'm trying to get to the bottom of an issue I'm seeing when
On Mon, 2018-04-09 at 15:10 +0100, Martin Townsend wrote:
> Hi Mimi,
>
> On Mon, Apr 9, 2018 at 1:46 PM, Mimi Zohar wrote:
> > On Mon, 2018-04-09 at 09:41 +0100, Martin Townsend wrote:
> >> Hi,
> >>
> >> I'm trying to get to the bottom of an issue I'm seeing when enabling
> >> the CAAM in the ker
Hi Mimi,
On Mon, Apr 9, 2018 at 1:46 PM, Mimi Zohar wrote:
> On Mon, 2018-04-09 at 09:41 +0100, Martin Townsend wrote:
>> Hi,
>>
>> I'm trying to get to the bottom of an issue I'm seeing when enabling
>> the CAAM in the kernel with IMA/EVM enabled. I'm using the official
>> NXP (imx_4.9.11_1.0.0
On Mon, 2018-04-09 at 09:41 +0100, Martin Townsend wrote:
> Hi,
>
> I'm trying to get to the bottom of an issue I'm seeing when enabling
> the CAAM in the kernel with IMA/EVM enabled. I'm using the official
> NXP (imx_4.9.11_1.0.0_ga) vendor Kernel.
>
> Here's the error message I'm getting.
>
>
Hi,
I'm trying to get to the bottom of an issue I'm seeing when enabling
the CAAM in the kernel with IMA/EVM enabled. I'm using the official
NXP (imx_4.9.11_1.0.0_ga) vendor Kernel.
Here's the error message I'm getting.
caam_jr 2142000.jr1: 4789: DECO: desc idx 7: Protocol Size Error -
A pr
22 matches
Mail list logo
