Alon Bar-Lev wrote:
> On 4/22/08, Douglas E. Engert <[EMAIL PROTECTED]> wrote:
>> I got the SCB built on Ubuntu and can now run it on XP. The command
>>  line programs work.
>>
>>  It works with FireFox 2.0.0.14. and IE 7.
>>
>>  With both, when I try an use the Windows "Safely Remove Hardware" icon
>>  with the smartcard still in the reader, I get the message "Problem
>>  Ejecting GemPC Card Reader" "The service 'Smart Card' is preventing this
>>  device from being stopped. Try stopping this service and then try to stop
>>  the device again."
>>
>>  If I remove the card first, both FireFox and IE let me safely remove
>>  the reader.
>>
>>  When I reinsert the reader and card , IE is able to use it again.
>>  FireFox is not. I had to restart Firefox to get this to work.
> 
> Please use my latest branch [1], it should fix this.

Oh, I though it was in the trunk. I have spent way to much time on this
over the last three weeks. But I will see what I can do.

> 
>>  I got it working with the IdAlly CSP and can use it to login to the Domain.
>>
>>  But this required some changes. When a CSP is run from Windows login,
>>  there is no stdout or stderr, no special environment variables, no
>>  HKEY_CURRENT_USER in the registry, and no path. The dlls must be in
>>  the system path, like: windows\system32 which is where the IDACSP.dll
>>  is, so I had to copy to system32:
>>
> 
> First of all there are keys at HKEY_LOCAL_MACHINE.

Yes, thats all you have to work with.

> I would have added the OpenSC bin directory to the path instead of
> copying these.
> 
>>  There may be issues with ssleay32 and libeay32 in system32 if
>>  other applications also require their own versions of these dlls.
> 
> I don't like to add new stuff into system32...

I don't either, but the  way I read this, the "application" is winlogin,
so the dlls have to either all be loaded with LoadLibraryEx, or
in the system path.

http://msdn2.microsoft.com/en-us/library/ms682586(VS.85).aspx?topic=306132

> 
>>  I also removed any paths for dlls in the registry:
>>  rather then using what was in sbin\opensc-install.bat
>>  I used:
>>
>>   Windows Registry Editor Version 5.00
>>  [HKEY_LOCAL_MACHINE\SOFTWARE\PKCS11-Spy]
>>  "Output"="c:\\temp\\pkcs11-spy.output.txt"
>>  "Module"="opensc-pkcs11.dll"
> 
> I don't really get this...
> 
>>  I am still playing around with the opensc.conf
>>  with debug, debug_file and error_file.
>>
>>  But I am pleasantly surprised to see that the Mingw cross
>>  complied dlls can be called from a CSP during winlogin!
> 
> Sure!
> I was trying to tell you, these are standard Windows executables.

Well have you ever gotten a CSP to call OpenSC during winlogin?
I wanted to see it work before believing, and there are still LoadLibrary
issues.

> 
> Alon.
> 
> [1] http://www.opensc-project.org/svn/opensc/branches/alonbl/pnp
> 
> 

-- 

  Douglas E. Engert  <[EMAIL PROTECTED]>
  Argonne National Laboratory
  9700 South Cass Avenue
  Argonne, Illinois  60439
  (630) 252-5444
_______________________________________________
opensc-devel mailing list
[email protected]
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to