Error 0x000000a0 / a0 (Bad password) can occur when using UPEK Fingerprint Reader
Case Scenario:
Using a UPEK Fingerprint reader for authentication can result in the error 0x000000a0, which mistakenly indicates a bad password. Functionally, it is somewhat like a bad password but it is important to understand why the user is not able to authenticate in this scenario. In the situation that a user registers his fingerprints on a UPEK biometric reader and then stores that information within the hard drive (as opposed to within the memory in the UPEK device), SecureDoc will not be able to access those registered fingerprints (because they're encrypted) and will produce the error 0x000000a0.
Probable Cause:
Since the fingerprint scans are used to validate the user's rights to log in in order to 'open up' the encryption key and read the disk, storing those fingerprint credentials within the 'still-encrypted' disk will produce a 'stand-off' situation:
The user can't authenticate to decrypt the disk because ...
... the information required to authenticate and decrypt is stored inside the encrypted disk.
In real-world terms, this is like storing directions to where to find your house key inside the locked house, except that there's no equivalent in SecureDoc to breaking a window to get in.
Product version affected:
Affects all versions of SD
UPEK Fingerprint Driver for Windows 7
Environment:
All Windows OS and Lenovo devices with UPEK Finger Print Reader
Solution:
When registering fingerprints using the UPEK middleware, ensure that the fingerprint information is stored only within the memory area within the UPEK device, and do not choose the option to store this information on the disk.
To resolve the immediate problem of access to the device, the administrator will need to create a keyfile on a USB stick that contains the device's key. After authenticating to that and getting access to Windows the user can re-register his fingerprints using the UPEK middleware and ensure that the registered fingerprint information is stored within the UPEK device's internal memory.
|
|