Re: 2nd try closed reg keys. make sure CryptSetProviderEx doesnt delete the 'Type XXX' key

[Alexandre Julliard]

James Hawkins <truiken(a)gmail.com> writes:
> Changelog
>  * make CryptSetProviderEx only delete the 'Name' value and not
> delete the entire 'Type XXX' key when deleting the default provider.

You are still leaking keys, and it doesn't even build (CryptCloseKey
is not a valid function). Please take your time, look over the code
carefully, fix all the leaks, then build and test it before
resubmitting. There's no hurry, you don't need to send a new patch
within 10 minutes of getting my mail <g>

-- 
Alexandre Julliard
julliard(a)winehq.org

2nd try closed reg keys. make sure CryptSetProviderEx doesnt delete the 'Type XXX' key

[James Hawkins]

hehe i'm sorry about the sill errors...I will look over it very
carefully this time and make sure all the leaks are gone.

On Fri, 27 Aug 2004 12:28:45 -0700, Alexandre Julliard
<julliard(a)winehq.org> wrote:
> James Hawkins <truiken(a)gmail.com> writes:
> > Changelog
> >  * make CryptSetProviderEx only delete the 'Name' value and not
> > delete the entire 'Type XXX' key when deleting the default provider.
>
> You are still leaking keys, and it doesn't even build (CryptCloseKey
> is not a valid function). Please take your time, look over the code
> carefully, fix all the leaks, then build and test it before
> resubmitting. There's no hurry, you don't need to send a new patch
> within 10 minutes of getting my mail <g>
>
> --
> Alexandre Julliard
> julliard(a)winehq.org

-- 
James Hawkins