Hi Mathias,
> Maybe there's something in that existing token.object that's not
> being properly (re)created via the invocation of `softhsm2-util`
> in d/rules?
Perhaps. I spent a couple of minutes looking at src:softhsm2. On my
machine at least, it seems to be deterministically different between
the two builds:
│ │ │ │ -00000000: 0000 0000 0000 0016 0000 0000 8000 5349 ..............SI
│ │ │ │ +00000000: 0000 0000 0000 0009 0000 0000 8000 5349 ..............SI
^^
However, I can't work out where these values are coming from. Given
that they are consistent, that would rule out uninitialised memory.
Given the actual values in binary (10110 vs 01001), they are likely
flags of some sort, perhaps from some kind of CONSTANT_A | CONSTANT_B
construction. Just braindumping in case it helps…
Best wishes,
--
,''`.
: :' : Chris Lamb
`. `'` [email protected] 🍥 chris-lamb.co.uk
`-
