Figure 2: Registration and Verification Phases
such as a birth certificate, driver license, etc. If suc-
cessful, a reference file is created for the registered
user. This involves storing samples of the user’s sig-
nature in a secure database. The user is provided with
a unique identifier (number or name) and any addi-
tional information pertinent to the verification proce-
dure.
Unlike other biometric systems, an individual’s sig-
nature tends to change over time due to various factors
such as age and health (Gupta and McCabe, 1997).
Therefore, the registration stage requires a method
to update a user’s reference file when needed after
his/her initial registration.
During verification an algorithm is run on a client’s
electronic signature. The electronic signature is com-
pared with the client’s reference file. The server logs
the outcome and notifies the client.
4 VERIFICATION ALGORITHM
This section contains a brief description of the verifi-
cation algorithm used in the scheme. Further details
can be found in (McCabe, 1997; McCabe, 2004).
The dynamic HSV approach consists of two sepa-
rate phases: conversion and comparison. The conver-
sion phase involves tracing the path of the signature.
It then examines several static and dynamic details of
the handwriting such as shape, spacing, velocity, ac-
celeration and timing details. These details are con-
verted into a string of characters (different characters
are used to represent different levels of velocity, ac-
celeration etc. and different aspects of shape, timing
etc.). The end result of this process is a string of sev-
eral hundred characters in length which attempts to
characterise the handwritten signature.
In order to compare two signatures it is possible
to use any one of a number of existing string dis-
tance algorithms to determine the level to which the
signatures differ. In (McCabe, 1997) several string
distance algorithms were implemented and experi-
mented with. The Wagner-Fischer algorithm (de-
scribed in (Stephen, 1994)) proved to be the most suc-
cessful.
In order to create a reference, a user of the system
is asked to provide five reference signatures on reg-
istration. The strings are extracted from each of the
reference signatures, each signature is compared to
one another and details of the common types and av-
erage levels of variation are recorded. When a test
signature is processed, it is compared to the reference
and a figure for the overall difference is calculated. If
this figure is below the threshold the test signature is
accepted as genuine, otherwise rejected as a forgery.
5 NETWORK SECURITY
In a network environment the signature data is at risk
from eavesdropping, interception, modification, fab-
rication and disruption. Measures such as encryption,
digital signatures and time stamping, are needed to
provide protection against these threats. This section
examines network security requirements for the HSV
scheme presented in this paper.
A client is provided with an initial session key, k
i
,
during registration. This allows encrypted communi-
cation with the server using any off-the-shelf symmet-
ric cryptosystem. Key updates are performed using
Diffie-Hellman key exchange (Diffie and Hellman,
1976).
The results of verification are signed using a digi-
tal signature (not to be confused with handwritten or
electronic signatures). S publishes a public key S
ku
.
This enables S to sign the results of verification using
the private key S
kr
. Anybody can verify the signature
using S
ku
. This can be achieved using RSA (Rivest
et al., 1978) or ElGamal (ElGamal, 1985) signatures.
Time stamping is required to prevent an intercep-
tor from resending captured messages. A time stamp
is appended to the handwritten signature data before
encryption. When a message is received, its time
stamp is examined to determine how old the mes-
sage is and if it has been previously received. This
presents a unique problem to HSV as any captured
electronic signature could be reused indefinitely. A
remedy stated in (McCabe, 2000), is to use a signed
password (rather than a signature) to verify a user.
This enables compromised handwritten passwords to
be changed, rather than handwritten signatures.
S logs all information regarding verification. Users
can access these logs in accordance with S’s policies.
REMOTE HANDWRITTEN SIGNATURE AUTHENTICATION
337