Re: CertGetCertificateChain() vs CertVerifyRevocation()
From: prem (anonymous_at_discussions.microsoft.com)
Date: 05/28/04
- Next message: Dale R: "Re: Using 128 bit AES (CALG AES 128) to generate session keys - problem"
- Previous message: Alon Bar-Lev: "Re: DPAPI protection credentials used with smartcard logons"
- In reply to: Vishal Agarwal[MSFT]: "Re: CertGetCertificateChain() vs CertVerifyRevocation()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 28 May 2004 03:06:06 -0700
Yes I am getting new CRL, I checked it by cleaning the Temporary Internet File folder and executed the program. I got a new CRL in the Temporary Internet File folder.
Now, if I try to run the same code in a loop i.e., trying CertGetCertificateChain() in a loop, I do not get the certificate as revoked. I tried stopping the program and started it, now I got the certificate as revoked.
I was told that there the CRL gets chached in the proces memory and I need to unload and load the crypt32.dll. But unfortunatley that idea does not suit to my application.
Is there any way to detect the real status of the certificate without restarting the program ?
Thanks,
Prem
- Next message: Dale R: "Re: Using 128 bit AES (CALG AES 128) to generate session keys - problem"
- Previous message: Alon Bar-Lev: "Re: DPAPI protection credentials used with smartcard logons"
- In reply to: Vishal Agarwal[MSFT]: "Re: CertGetCertificateChain() vs CertVerifyRevocation()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|