Re: New proposed solution to the QC biometric issue

[Petra Gloeckner <Petra.Gloeckner@xxxxxxxxxxxxxxxx>]

Hi Stephen,

Stephen Farrell wrote:
> 
> - you'll need an algo id somewhere or you can't recalc. the
> hash

yes, I agree. So I correct my ASN.1 definition of the BiometricData:

BiometricData ::= SEQUENCE { 
         typeOfBiometricData  OBJECT IDENTIFIER 
	 hashalgorithm	      AlgorithmIdentifier
         biometricDataHash    OCTET STRING }
 
> - you'll need to specify how the actual data is to be
> flattened before hash calculation (e.g. strip CR/LF or
> whatever), this could be incorporated with the
> algo id (so use a transform id)

As I understood the whole discussion the reference data has been 
provided before, i.e. it is already existing and pre-stored. 
There is no new verification data which needs to be transformed 
and compared against the reference data. The purpose of the 
biometrics extension is just to verify by a signed message that 
the provided reference data belongs to the certificate holder.

Correct me, if I'm wrong!

Petra