Catch SIGINT, SIGQUIT and SIGTSTP but ignore during the database

update.  We have to be careful and drop our lock if we are suspended
and then regain the lock on resume.  This is necessary because the
user must not be allowed to keep a record locked for a long period
of time to avoid a DoS.  We must be sure to re-lock when we resume
because otherwise an attacker could suspend us until a user starts
to login and then resume and then race the user for login using
the challenge response from the user.

0 files changed, 0 insertions, 0 deletions