Re: .NET CryptoAPITransform and KeyHandle interop

From: Michel Gallant (neutron_at_NOSPAMistar.ca)
Date: 12/19/03 

Date: Fri, 19 Dec 2003 08:22:03 -0500

Thanks Ivan,
Any answers to my other specific questions on KeyHandle functionality
in .NET 1.1 ??
Thanks,
 - Mitch

"Ivan Medvedev [MS]" <ivanmed@online.microsoft.com> wrote in message
news:OEAPBOexDHA.3224@tk2msftngp13.phx.gbl...
> Michel -
> it depends on the version. In Whidbey (tech preview was made available at
> the PDC) this will be specified with CspProviderFlags.
> --Ivan
> http://blogs.dotnetthis.com/ivan
>
> "Michel Gallant" <neutron@NOSPAMistar.ca> wrote in message
> news:OX0YyZXxDHA.3220@tk2msftngp13.phx.gbl...
> > I understand that CryptoAPITransform.KeyHandle returns a
> > handle to the native symmetric key handle (for underlying capi
> > CSP like RC2, TripleDES etc..)
> >
> > There is no problem acquiring such a keyhandle in managed code:
> >
> > CryptoAPITransform capitrans = (CryptoAPITransform) encryptor ;
> > IntPtr hsymkey = capitrans.KeyHandle ; //native key handle
> >
> > but this keyhandle fails when supplied to CryptoAPI functions via Pinvoke
> > (typically with Bad Key error).
> > Anyone with experience here?
> >
> > Is the underlying SymmetricAlgorithm keyhandle marked as "Exportable" in
> > capi? SymmetricAlgorithm classes don't seem to have properties that allow
> > controlling some dwFlags that CryptoGenKey() does.
> >
> > Thanks,
> > - Mitch Gallant
> > MVP Security
> >
> >
>
>