Danielle Madeley

Something is wrong with the length of that type. I would start by having a look how long the value `v` is. Also what item `v` refers to.

Okay so I'm guessing it's a mismatch between how long Python thinks an L is and how long PKCS#11 thinks an L is. Is one being compiled for a different...

We'll assume the PKCS#11 module is correct. But that our compilation of the headers might be wrong. Especially if the LFS machine is missing some #define (those headers are full...

It feels a lot like what is being #defined to set all of the sizes. Did anyone check the sizes of types in the compile?

No. You want to be using native sizes and endianness, not standard sizes. The definition from PKCS#11 for `CK_ULONG` is: ``` typedef unsigned long int CK_ULONG; ``` Which is your...

That's not strictly true here. You have a C calling convention defined by your operating system that defines the lengths of types, endianness, etc. Else you'd never be able to...

I am not an expert on the PKCS#11 spec by any means, but I think you've misunderstood things. By word alignment errors, I take it to mean alignment within the...

Hi, I don't know the specifics of the Thales Luna. You will need to consult the documentation for how the HSM maps to the semantics of PKCS#11. `pkcs11-tool` can help...

This error comes from the HSM. Some pkcs11 libraries have an environment variable to output more information to stderr. One guess would be that you may need to supply `key_length`....

In this case I think you're going to have to take care of it. We can't control how sessions to the HSM device are handled, since they're all handled separately.