which dlls need to be updated to support latest Eid cards?

[Kristof Eykens]

beid40cardlayer.dll

beid40common.dll

beid40DlgsWin32.dll

beidmdrv.dll

beidpkcs11.dll

BouncyCastle.Crypto.dll

Net.Pkcs11.dll

Net.Pkcs11.EtokenExtensions.dll

[Frederik Vernelen]

For the SDK applications (and other applictions that use pkcs11 (e.g. firefox)):

beid40cardlayer.dll

beid40common.dll

beid40DlgsWin32.dll
beidpkcs11.dll

For applications that use the minidriver (e.g. internet explorer, google chrome, )

beidmdrv.dll

--
You received this message because you are subscribed to the Google Groups "eID Middleware Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eid-middleware-...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kristof Eykens]

Ok thanks!

I pulled the sources for middleware from http://eid-mw.googlecode.com/svn/trunk/ eid-mw-read-only and rebuild the solution in release without dialog.

This builds only the beidpkcs11.dll and beidmdrv.dll. The other files I still use from the sdk dll build in 2012.

So is the beidpkcs11.dll and beidmdrv.dll enough to get the latest eid cards to work? Because the sdk download is still the same from 2012.

[Frederik Vernelen]

Hello,

Well, the latest version of the middleware is  version 407 (under https://code.google.com/p/eid-mw/source/browse/#svn%2Fbranches%2F4_0_7%253Fstate%253Dclosed)

Not all changes there are backported to the trunk yet, I'll do that today.

Though the version in the trunk should be working with new cards to.

In the trunk, the beid40cardlayer., beid40common and beid40DlgsWin32.are build as static libraries and are included in beidpkcs11.dll.

So beidpkcs11.dll should be enough to build your SDK application.

The SDK download is basically the manual and examples (and pkcs11 headers, but they're still the same), the libraries you need are installed by the middleware installer.

Wkr,

 Frederik

--

[Kristof Eykens]

Ok thanks for the clarification!

In my other post "Problem with new beidpkcs11.dll", I noticed when I put all the dlls as described above to my .net application the card reader still works (with the newly build beidpkcs11.dll). But when I delete all the dlls except beidpkcs11.dll. (installed latest middleware) Then the driver starts behaving weird and I start getting the following error. When I copy back the dlls from the sdk 4.0 it works again. So something must be changed in the session management or something...

 Net.Sf.Pkcs11.TokenException: DEVICE_ERROR

   bij Net.Sf.Pkcs11.Wrapper.Pkcs11Module.FindObjectsInit(UInt32 hSession, CK_ATTRIBUTE[] pTemplate)

   bij Net.Sf.Pkcs11.Session.FindObjectsInit(P11Attribute[] attrs)

   bij SunCoach.Client.Eid.Logic.EidReader.GetData(String type)

The only thing I do in the code is use the waitForEvent to check if a card is inserted or removed, to create .net events from this. Now I cannot reuse the Module or Session --> code recreates sessions when a session is already open.

[Kristof Eykens]

Ok I got closer to the problem, previously _module.WaitForSlotEvent(false) only triggered once when inserting a eid card. With the latest version I get 2 events which messes with my custom code.

Is there a reason why an insert of a card is now triggering twice?

[Frederik Vernelen]

In the past we had some filters in place that would block certain events we got from SCardGetStatusChange, but then we faced the issue that sometimes too much was filtered out (it depends on the os how many events were sent))

So we decided to pass all the events we receive upwards.

I'll do some tests with it, and see if we can't group multiple events that belong together.

On Mon, Jun 2, 2014 at 10:17 PM, Kristof Eykens <kristof...@gmail.com> wrote:

Ok I got closer to the problem, previously _module.WaitForSlotEvent(false) only triggered once when inserting a eid card. With the latest version I get 2 events which messes with my custom code.

Is there a reason why an insert of a card is now triggering twice?

--