EldoS | Feel safer!

Software components for data protection, secure storage and transfer

Multiple PIN entering for crypto card

Also by EldoS: Callback File System
Create virtual file systems and disks, expose and manage remote data as if they were files on the local disk.
Posted: 02/18/2009 08:45:00
by Szymon Piskula (Basic support level)
Joined: 02/05/2009
Posts: 17

I woud like refer to [URL=http://eldos.com/forum/read.php?FID=7&TID=771&MID=4085&phrase_id=358185#message4085]this topic[/URL] to part
With ElWinCertStorage your code accesses CryptoAPI. SmartCard drivers provide so-called CSPs to CryptoAPI. The CSPs ask for the pin themselves and usually cache the pin for application session lifetime so that the the user doesn't need to enter the pin multiple times. As said, this is specific to the driver.

When does the application session start when using ElWinCertStorage ? Could you please point it on the example of TinySigner? How would look the process of signing multiple PDF's with only one pin entrance, providing that the driver allows caching of pin for the session?

Posted: 02/18/2009 09:10:34
by Eugene Mayevski (EldoS Corp.)

Szymon Piskula wrote:
When does the application session start when using ElWinCertStorage ?

It's different for every token. Some token drivers might ask the pin when the user accesses the token itself, others will ask for it when the protected information (the private key) is accessed. Also pin entry is beyond your control (in case of CryptoAPI). So the rest of your questions are just not applicable. If you want to control PIN entry, you need to use PKCS#11 interface instead of CryptoAPI.

Sincerely yours
Eugene Mayevski



Topic viewed 934 times

Number of guests: 1, registered members: 0, in total hidden: 0


Back to top

As of July 15, 2016 EldoS Corporation will operate as a division of /n software inc. For more information, please read the announcement.

Got it!