In order to check if the inserted card is a genuine eID card, you'll have
to request the data files and verify the signatures, as well as checking
the validity of the certificates.
The Integrety class of our CS examples could give you an idea about this.
Good to hear so.
In the SDK 4.0, a message to ask permission to read the card will be shown
each time a session to a card is opened (and data is requested to be read).
So if you do all your reads (from one card) within the same session, the
message should be show only once (per card).
For each newly inserted card, permission to ask the card will always be
asked again.
On Wed, May 9, 2012 at 3:12 PM, Dieter Cams <dieter.c...@gmail.com> wrote:
> Bedankt voor de snelle respons.
> We hebben het aan het werken gekregen. Er is enkel 1 probleempje waardoor
> het voor ons trager lijkt: in onze vorige applicatie moesten we maar 1 maal
> de toestemming geven om een eid te lezen. Nu moeten we dit bij elke read
> doen. Is hiervoor nog een oplossing?
> Mvg
> Dieter
> Verzonden met mijn Windows Phone
> ------------------------------
> Van: Frederik Vernelen
> Verzonden: 9-5-2012 10:39
> Aan: Dieter Cams
> CC: eID Middleware Dev
> Onderwerp: Re: [eid-mw-dev] Re: Updating an older EID app
> Hello Dieter,
> You can suppress this message by creating and setting following registry
> key to zero: HKEY_CURRENT_USER\Software\BEID\messages\show_sdk35_warning
> In regard to the speed: are you refering to a C# project that does all the
> validity checking?
> Wkr,
> Frederik
> On Wed, May 9, 2012 at 10:14 AM, Dieter Cams <dieter.c...@gmail.com>wrote:
>> I think it is by far harder to implement the new EID than the old one.
>> Our experiences is also that the new EID-software is slower than the
>> old one.
>> Is it possible to still use the EID3.5 without getting the message
>> that there is a newer version?