Chipcard CryptTokens
[Libchipcard3 Client Library]

Collaboration diagram for Chipcard CryptTokens:

---

Detailed Description

Chipcard-based CryptTokens.

Libchipcard2 provides CryptToken plugins for Gwenhywfar. These plugins can be used by AqBanking.

The following CryptToken plugins are provided:

• DdvCard (supports DDV0 and DDV1 cards)
• StarcosCard (with subtypes starcoscard-vr and starcoscard-hvb)

Functions for Inheriting Classes
Functions in this group can be used by other card based CryptToken plugins.
CHIPCARD_API int	LC_CryptToken_VerifyPin (GWEN_PLUGIN_MANAGER *pluginManager, GWEN_CRYPTTOKEN *ct, LC_CARD *hcard, GWEN_CRYPTTOKEN_PINTYPE pt)
CHIPCARD_API int	LC_CryptToken_ChangePin (GWEN_PLUGIN_MANAGER *pluginManager, GWEN_CRYPTTOKEN *ct, LC_CARD *hcard, GWEN_CRYPTTOKEN_PINTYPE pt, int initial)
CHIPCARD_API int	LC_CryptToken_ResultToError (LC_CLIENT_RESULT res)

---

Function Documentation

CHIPCARD_API int LC_CryptToken_VerifyPin	(	GWEN_PLUGIN_MANAGER *	pluginManager,
		GWEN_CRYPTTOKEN *	ct,
		LC_CARD *	hcard,
		GWEN_CRYPTTOKEN_PINTYPE	pt
	)

Let the chipcard verify a pin. If the card reader has a keypad then secure input will be used. Otherwise the user will be asked to enter a pin which is then relayed to the card.

CHIPCARD_API int LC_CryptToken_ChangePin	(	GWEN_PLUGIN_MANAGER *	pluginManager,
		GWEN_CRYPTTOKEN *	ct,
		LC_CARD *	hcard,
		GWEN_CRYPTTOKEN_PINTYPE	pt,
		int	initial
	)

Let the chipcard change a pin. If the card reader has a keypad then secure input will be used. Otherwise the user will be asked to enter a pin which is then relayed to the card.

CHIPCARD_API int LC_CryptToken_ResultToError

(

LC_CLIENT_RESULT

res

)

Convert the given client result code to one of Gwenhywfars error codes.