On Fri, 2016-02-05 at 16:58 +0100, Carsten Wolff wrote: > On Friday 05 February 2016 01:10:37 Ben Hutchings wrote: > > I found what seems to be a bug in the driver, but it was present in > > both 3.2 and 3.16. Please test whether the attached patch fixes this > > issue > > Hum, the patch only fixes the decision, if and when the key is reset before an > operation, but not, which cword is used in actual operations, right? So it > shouldn't change anything in the result? Apparently if this is not done when switching keys, the Padlock unit might use stale data derived from the previous key. However, I don't think it's a huge risk in practice. > At least, it does not fix the error > I'm seeing. The message stays the same, including the 32 byte it dumps. Then I'm out of ideas. I'll pass this to the upstream developers. Ben. -- Ben Hutchings It is a miracle that curiosity survives formal education. - Albert Einstein
Attachment:
signature.asc
Description: This is a digitally signed message part