🚀 go-pugleaf

A summary of the problem: The token I'm using will automatically log
out after a successful signing operation (i.e. C_Sign or C_SignFinal
and signature is returned). That causes Adobe Reader 8 to crash. The
token is made by a third party so I can't change its behavior.

The long story follows.

I am developing a PKCS#11 module for using a specific smart card. The
module works perfectly if I use it via my commandline testing program,
but have problems working with Adobe Reader.

I found that the document is signed and saved properly -- I can open
the document later and its signature can be verified. However Adobe
Reader always crash (0xC00000005) after signing.

In my PKCS#11 module I logged how Adobe Reader calls it, and found the
C_Sign call is made successfully. After that, there is a series of
slots and objects querying just before the crash.

I know the token I'm using will logout after a successful signing
operation, and I guess it might be the cause. I added code to
automatically re-login after signing, and this solves the problem - no
more crash.

It seems to me that Adobe Reader is caching information about the
slots, tokens, keys and certs... and if those information is changed
while Adobe Reader does not expect it, Adobe Reader can't handle it and
crash.