[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ms-cryptoapi
Subject:    Re: CryptSetProvParam not called
From:       John Banes <jbanes () MICROSOFT ! COM>
Date:       1996-12-30 9:45:01
[Download RAW message or body]


Kevin,

It is as you say, and the hProv parameter is always ignored when the
CryptSetProvParam function is called with PP_CLIENT_HWND.

>-----Original Message-----
>From:  Kevin Kooy [SMTP:krk@WWW.SSE.ATT.COM]
>Sent:  Thursday, December 26, 1996 7:51 AM
>To:    CryptoAPI@LISTSERV.MSN.COM
>Subject:       Re: CryptSetProvParam not called
>
>The PP_CLIENT_HWND (==1) option is not passed down to the CSP.
>It is evidently state that is held by advapi32.dll.
>This is to allow an app to use this option before calling
>CryptAcquireContext so that a window handle can be given to
>whatever CSP is selected when CryptAcquireContext does get called.
>CSPs do an upcall to get the HWND to use for authentication, etc.
>
>Question:
>When an application does this early PP_CLIENT_HWND call,
>is the hProv parameter ignored?
>
>--
> Kevin R. Kooy
> AT&T
> kevin.kooy@att.com
>--
>
>
>----------
>From:   James F. Weber[SMTP:jweber@MINNETONKASOFTWARE.COM]
>Sent:   Friday, December 20, 1996 5:10 PM
>To:     jtg@www.sse.att.com; krk@www.sse.att.com
>Subject:        CryptSetProvParam not called
>
>My CSP is not getting the CryptSetProvParam call.  However, the CAPI
>call returns TRUE.  The provider handle is valid, I have debug
>statements and blatant execution indicators in the CSP code, etc. but
>the call does not make it to the CSP.  I am passing a dwParam value of
>1.  Any ideas?
>
>Thanks,
>Jim Weber
>
>--
>James F. Weber                    Phone:   612-449-0187
>Minnetonka Software, Inc.         Fax:     612-449-0318
>James.Weber@MinnetonkaSoftware.com

[prev in list] [next in list] [prev in thread] [next in thread]