TPM token fails to reinitialize properly on reload
Bug #645576 reported by
David Smith
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openCryptoki |
Unknown
|
Unknown
|
|||
opencryptoki (Debian) |
Fix Released
|
Unknown
|
|||
opencryptoki (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Won't Fix
|
Undecided
|
Unassigned | ||
Natty |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: opencryptoki
The TPM token code uses some global variables to track the storage root key, root public & private keys, and leaf public & private keys from the TPM. These variables are not properly reinitialized during unload and reload of the module. In the case of wpasupplicant, this results in PKCS#11 becoming unusable and one must kill the process to start a fresh reconfiguration.
Attached is a patch that cleans up the use of these variables in the token_specific_
tags: | added: glucid |
tags: | added: patch |
Changed in opencryptoki (Debian): | |
status: | Unknown → New |
Changed in opencryptoki (Debian): | |
status: | New → Fix Released |
tags: | added: verification-done-lucid |
Changed in opencryptoki (Ubuntu Natty): | |
status: | Fix Committed → Won't Fix |
Changed in opencryptoki (Ubuntu Maverick): | |
status: | Fix Committed → Won't Fix |
To post a comment you must log in.
Also attaching debdiff from fixed package.