|
|
£1040.00
|
|
 |
U.are.U
Pro Software
Development
Kit (Gold)
|
|
For
Windows®
2000®, NT
4.0®, Me,
‘98®, and
‘95® (with
USB support)
systems
|
|
|
Pro
Software Development
Kit (Gold Edition)
Digital
Persona’s Gold Software Development Kit (SDK)
enables developers to add the power of fingerprint
authentication security to their Windows applications.
The toolkit includes header files that define
the API, sample code for Visual C++ 6.0, and
the Fingerprint Recognition Engine runtime.
For customers who use Visual Basic to develop
programs it will be necessary to use our DCOM
SDK or to wire a wrapper to package our DLL
for their use.
WHO
IS IT FOR?
System Integrators
– The SDK
can be used to
develop custom
applications for
a wide variety
of security use
related to PC
or client/server
access. Basically
any application
that runs on a
PC or is controlled
by a PC that needs
user authentication
can use the U.are.U
® SDK.
Application
Developers –
Anyone who is
developing an
application to
be distributed
widely can include
links to U.are.U
for user administration
and authentication.
If your customer
uses a U.are.U
sensor, your application
will take advantage
of it.
WHO
IS IT NOT FOR?
The
SDK is designed to develop application that
run on the Windows platform. If you have
application where a PC running Windows will
not be present, please contact us for additional
information. Also, the standard shipping
version of the SDK will work with Digital
Persona sensors.
WHAT
IS THE ARCHITECTURE
OF THE SDK AND
THE FINGERPRINT
ENGINE?
There
are several components to the Digital Persona
Fingerprint Engine, as exposed by the SDK.
The application developer is provided with
several levels of API’s, from the low-level
interface to high-level authentication functions.
The Fingerprint
Engine interacts
directly with
the U.are.U sensor
COM Server. The
Server handles
all sensors connected
to the USB ports
and dispatches
notification of
fingerprint capture
to all U.are.U-enabled
applications running
on the system.
There can be multiple
sensors, up to
127 as defined
by the USB specification,
attached to the
system. The Server
sets up a challenge/
response encrypted
link with the
sensor to securely
transfer the image
from the sensor.
FINGERPRINT
ENGINE COMPONENTS
The
Feature Extraction
Module:
The
Feature Extraction
Module extracts
a template from
the fingerprint
image that comes
from the sensor.
The size of this
template is approximately
250 bytes. The
feature extraction
process takes
approximately
0.6 seconds on
a Pentium 200.
The Feature Extraction
Module will also
return diagnostic
information about
the quality of
the fingerprint
captured, for
instance if the
contrast is not
adequate, or if
it contains too
little information
for a reliable
match. The Feature
Extraction Module
has been designed
in such a way
as to allow input
from other fingerprint
capturing devices.
The
Matching Module:
The Matching Module
will take two
fingerprint templates
and perform a
match. If a match
is confirmed it
will also return
a l28-bit string,
which could be
used as a unique,
reproducible cryptographic
key for that user’s
finger. The Matching
Module will also
return the quality
of the match.
The application
can set security
level (false accept
rate) for future
matches. The default
security settings
are 0.01% chance
of false accept
vs 1.4% chance
of false reject
for single finger
match attempt.
The template match
process takes
approximately
0.1 seconds on
a Pentium 200.
The Matching Module
is also able to
perform learning
upon successful
match. Learning
requires extra
computation and
can be switched
on and off by
the application.
The
Database Module:
The
Database Module
can be used to
store and manage
a user database
for fingerprint
templates and
user attributes.
The user record
contains multiple
fingerprints from
the user, and
a protected storage
area where data
such as passwords
or cryptographic
keys can be securely
stored for each
user - only accessible
by the user through
a correct fingerprint
match. The Database
Module is included
as a convenience
for developers
who wish to create
a standalone application.
However, fingerprint
templates and
user records can
be stored in any
location the developer
chooses, such
as an extension
to a digital certificate,
within a LDAP
directory, or
in the NT SAM
user database.
The
High Level Interface
Module:
This
is the only API that the developer needs
to interact with. It calls the sensor server
and the rest of the modules. There are high
level calls for registration and verification.
After initializing the Engine, the developer
only needs to call a single registration
function whenever a new fingerprint is to
be registered. Yet, Digital Persona does
not display its own user interface. The
Engine will perform a callback to user interface
functions that are provided by the developer,
so the developer can maintain a consistency
of interface in the developed application
Security
and Privacy Measures:
For
all of the above modules, Digital Persona
has given paramount consideration to security
and user privacy issues. For instance, at
no time are the unencrypted templates or
user records passed across library interface
functions, exported or stored in a database.
Furthermore, registration templates cannot
be matched against themselves — which means
the user must provide a current new sample
for matching. At the time of installation,
a security key is entered by the user and
it is used internally as part of the encryption
schema of the Fingerprint Engine. Templates
that are created on different computers
using different security keys are not compatible
|
