Alon Bar-Lev wrote: > On 4/23/08, Douglas E. Engert <[EMAIL PROTECTED]> wrote: >>> 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 > > Again, why not add this to the system PATH?
I don't believe you can during winlogin. This is also called by a CSP, that is residing in system32. Keep in mind that if OpenSC is to be adopted by Windows User, Admins, Auditors and Security people, it better be very standard, have an installer and not go around changing system paths. Its already looking to much like unix for some of these people. > >> 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. > > It is standard DLL, it is not important. > There are no issues I am aware of. > > Alon. > > -- 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
