FpVTE2012 Validation

The contents of this validation package aims to help prepare your code for submission to NIST's FpVTE2012 evaluation.

INSTRUCTIONS TO PARTICIPANT

1. Install the libbiomeval RPMs (rpm -ihv ./rpm/*).
   • If you have already installed older versions, use rpm -Uhv instead to perform an update.
2. Run make at the root of this validation package to build linking the "Null SDK." This SDK simply returns successfully from each method.
3. Copy your library into the "lib" directory at the root of this validation package, changing the value of LIBSDK on line 20 of ./src/drivers/Makefile to the name of your library submission, so that it may be properly linked to the validation drivers.
   • Ensure you relink (cd ./src/drivers/ && make clean all && cd -)
4. Run ./scripts/class_[abc].sh and encrypt and send the resulting .tar.gz to fpvte@nist.gov
   • If you are a class A participant, run only class_a.sh, etc.

WALKTHROUGH

The following is a sample walkthrough of the validation step for a Class A participant. Unless otherwise specified, all commands are run from the root of the validaiton package (the directory containing this README).

1. Install RPMs
   • rpm -ihv ./rpm/*
2. Build validation driver with nullSDK
   • make
3. Build and copy participant library, libFpVTE12_TEST_A_1_1.so to ./lib
   • cp ~/devel/libfpvteTestSDK.so ./lib
4. Change ./src/drivers/Makefile to link against participant library
   • Change line 20 to read LIBSDK = FpVTE12_TEST_A_1_1
   • If you must modify the build procedure here to link against any other third-party libraries, you must inform the test liaison.
5. Relink the validation driver
   • cd ./src/drivers/ && make clean all && cd -
6. Run the Class A validation script
   • ./scripts/class_a.sh
7. Encrypt the resulting tar file and send to NIST.
   • File is named ./output-classA-FpVTE12_TEST_A_1_1.tar.gz
   • http://www.nist.gov/itl/iad/ig/encrypt.cfm

SIGNIFICANT FILES

• src/include/fpvte2012.h
  • Header file for the evaluation. All core methods your submission must implement are declared within.
• src/nullsdk
  • An FpVTE2012 implementation that does nothing except return successfully. You may use this as a starting point for your code.
• bin/ (once built)
  • Binaries to minimally exercise the basic calling structure of enrollment and identification for the FpVTE2012 evaluation.
• scripts/
  • Scripts to generate a Properties file used to drive the enrollment and identification validation drivers.
• data/
  • The datasets, in the form of RecordStores, that will be used for validating your submission.

IDENTIFICATIONS PERFORMED

• Class A:
  • ./data/class_a/1fL_search vs ./data/class_a/1fL_enroll
  • ./data/class_a/1fR_search vs ./data/class_a/1fR_enroll
  • ./data/class_a/2f_search vs ./data/class_a/2f_enroll
• Class B:
  • ./data/class_b/10f_search vs ./data/class_b/10f_enroll
  • ./data/class_b/4fL_search vs ./data/class_b/10f_enroll
  • ./data/class_b/4fR_search vs ./data/class_b/10f_enroll
  • ./data/class_b/8f_search vs ./data/class_b/10f_enroll
• Class C:
  • ./data/class_c/10r_search vs ./data/class_c/10r_enroll
  • ./data/class_c/10p_search vs ./data/class_c/10p_enroll
  • ./data/class_c/10p_search vs ./data/class_c/10r_enroll

BUILDING

A make at the root of this package will build everything, linking the nullSDK to the validation drivers. Change the name of the library to the name of your SDK on line 20 of ./src/drivers/Makefile to exercise your own code.

QUESTIONS

Please e-mail fpvte@nist.gov.

17 July 2012