Hi Herbert,
The SPAcc crypto accelerator has the below design
1. The SPAcc does not allow us to read internal context (including
the intermediate hash).
The hardware context is inaccessible for security reasons.
2. SPAcc has multiple hardware contexts and every request uses a hardware
context that's obtained using 'spacc_open' and released with
'spacc_close'.
The export/import is supposed to save the intermediate hash and
since SPAcc hardware
does not provide that, I was using it to save my driver state. This
is redundant and I tested
the same by removing it from export/import. An empty import/export
function is what I
have in the latest driver code and that works for me.
Appreciate your inputs.
Warm regards,
PK
On Fri, May 10, 2024 at 1:33 PM Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> wrote:
>
> On Tue, May 07, 2024 at 09:49:57AM +0530, Pavitrakumar Managutte wrote:
> >
> > About the export function, yes its hash state that's present inside
> > "spacc_crypto_ctx".
>
> Please show me exactly where the partial hash state is stored in the
> request context because I couldn't find the spot. It can't be in
> spacc_crypto_ctx as that is the tfm context and shared by multiple
> reqeusts.
>
> Thanks,
> --
> Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
