Karl,
I don't understand then why even have a CHVDialog interface and allow
the card services object to have a method that lets the CHVDialog be set? I
looked through the code and it is never used. I figured that the
implementation of the card services by the card provider would make use of
it but after looking into Gemplus's code I realized it is an unused object.
Is this true? In fact somewhere down deep in the guts of the code, in
GPKTransientPINHolder, a DefaultCHVDialog is created which totally ignores
the fact that a caller set the one thought to be used in SignatureService
which is derived from CardService where the call is exposed from.
Any ideas on what the reasoning was behind having such an interface to
begin with if OCF is going to prompt the user for the password in any case?
Chris
-----Original Message-----
From: Karl Scheibelhofer <[EMAIL PROTECTED]>
To: Christopher Fahey <[EMAIL PROTECTED]>
Date: Thursday, November 02, 2000 4:33 PM
Subject: RE: [OCF] Wheres the PIN (Using OCF and Gemplus)?
>hi,
>
>> Karl,
>> Do you know of any other way to make the Gemplus OCF request user pin
>> callback stuff work in a manner that makes less use of the GPK code?
>
>unfortunately, there is no standard way to do this in the current version
of
>OCF. they plan to introduce this in a future version. see
>http://www.opencard.org/work/rfc-14/rfc-14.txt
>
>regards
>
> Karl Scheibelhofer
>
>--
>
>Karl Scheibelhofer, <mailto:[EMAIL PROTECTED]>
>Institute for Applied Information Processing and Communications (IAIK)
>at Technical University of Graz, Austria, http://www.iaik.at
>Phone: (+43) (316) 873-5540
>
---
> Visit the OpenCard web site at http://www.opencard.org/ for more
> information on OpenCard---binaries, source code, documents.
> This list is being archived at http://www.opencard.org/archive/opencard/
! To unsubscribe from the [EMAIL PROTECTED] mailing list send an email
! to
! [EMAIL PROTECTED]
! containing the word
! unsubscribe
! in the body.
