[PATCH v2] crypt32/tests: Add a test to verify certificate signature.

[Hans Leidekker]

On Wed, 2021-04-14 at 12:24 +0300, Dmitry Timoshkov wrote:
> Hans Leidekker <hans at codeweavers.com> wrote:
> 
> > On Wed, 2021-04-14 at 11:59 +0300, Dmitry Timoshkov wrote:
> > > +static NTSTATUS (WINAPI *pBCryptCloseAlgorithmProvider)(BCRYPT_ALG_HANDLE, ULONG);
> > > +static NTSTATUS (WINAPI *pBCryptCreateHash)(BCRYPT_ALG_HANDLE, BCRYPT_HASH_HANDLE *, PUCHAR, ULONG, PUCHAR,
> > > +                                            ULONG, ULONG);
> > > +static NTSTATUS (WINAPI *pBCryptDestroyHash)(BCRYPT_HASH_HANDLE);
> > > +static NTSTATUS (WINAPI *pBCryptDestroyKey)(BCRYPT_KEY_HANDLE);
> > > +static NTSTATUS (WINAPI *pBCryptFinishHash)(BCRYPT_HASH_HANDLE, PUCHAR, ULONG, ULONG);
> > > +static NTSTATUS (WINAPI *pBCryptHashData)(BCRYPT_HASH_HANDLE, PUCHAR, ULONG, ULONG);
> > > +static NTSTATUS (WINAPI *pBCryptGetProperty)(BCRYPT_HANDLE, LPCWSTR, PUCHAR, ULONG, ULONG *, ULONG);
> > > +static NTSTATUS (WINAPI *pBCryptOpenAlgorithmProvider)(BCRYPT_ALG_HANDLE *, LPCWSTR, LPCWSTR, ULONG);
> > > +static NTSTATUS (WINAPI *pBCryptVerifySignature)(BCRYPT_KEY_HANDLE, VOID *, UCHAR *, ULONG, UCHAR *, ULONG, ULONG)
> > 
> > Do we need to load these dynamically? It looks like they're all
> > supported since Vista.
> 
> I just decided to follow what bcrypt tests are doing. If that's preferrable -
> I can cetainly remove the dynamic linking.

I believe the bcrypt tests do that mostly for historical reasons (it
does use one or two exports that were added after Vista). Here there's
no need for dynamic linking it seems.