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

List:       ms-cryptoapi
Subject:    Re: rsaenh.dll and service pack 3
From:       gweissman <gweissman () SPYRUS ! COM>
Date:       1997-07-25 16:52:46
[Download RAW message or body]


If I recall correctly, that's the result of an access violation; ADVAPI32
traps the fault and returns error (0x57)


At 12:08 PM 7/24/97 -0700, you wrote:
> Here is a little more detail.
>I am using the enhanced provider with service pack 2. I run hash a test on
>CALG_MD5 using the enhanced provider and then I re-run the same test on my
>CSP and compare the resulting hash values. I repeat a series of data sizes
>and block size combinations in this test. I then repeat the same set of
>tests on CALG_SHA. Everything works fine with the service pack 2 csp. When I
>run this same test on the service pack 3 enhanced csp I get the following:
>
>CryptCreateHash fails eith error : 0x57
>I am passing CALG_SHA (value 0x00008004), the same value as used in the
>service pack 2 csp.
>
>Has anyone seen this? Has the CALG_SHA value changed?
>
>Thanks
>
>Greg
>
>
>-----Original Message-----
>From: Jeff Spelman <jeffspel@MICROSOFT.COM>
>To: CryptoAPI@LISTSERV.MSN.COM <CryptoAPI@LISTSERV.MSN.COM>
>Date: Wednesday, July 23, 1997 5:16 PM
>Subject: Re: rsaenh.dll and service pack 3
>
>
>
>>Greg
>>   I'm not aware of any problems or changes in the SHA1 implementation
>>from SP2 to SP3.  The Enhanced provider which comes with SP3 definitely
>>supports SHA1.  There is a bug with the MS Enhanced Provider which is
>>that the signature for the provider was not put into the registry,
>>however this would cause a failure at CryptAcquireContext, if this
>>succeeds then that is not your problem.  What exactly is failing?
>>
>>Thanks, Jeff
>>
>>> -----Original Message-----
>>> From: Greg Powell [SMTP:g.powell@IX.NETCOM.COM]
>>> Sent: Wednesday, July 23, 1997 4:43 PM
>>> To:   CryptoAPI@LISTSERV.MSN.COM
>>> Subject:      rsaenh.dll and service pack 3
>>>
>>>  I am having trouble with the enhanced provider that came with service
>>> pack
>>> 3. I have been developing a CSP and testing it against the enhanced
>>> CSP that
>>> came with service pack 2. Everything works fine. But service pack 3
>>> seems to
>>> have a problem with SHA1. Does the provider that comes with service
>>> pack 3
>>> not support sha1? Or is the defined constant for sha1 different in
>>> service
>>> pack 3 than service pack 2?
>>>
>>> Greg
>>>
>>>
>>>
>>> g.powell@ix.netcom.com
>>> http://www.rnbo.com - Rainbow Technologies
>>> http://isg.rnbo.com - Rainbow Technologies, Internet Security Group
>>>
>>> ----------------------------------------------------------------
>>> Users Guide http://www.microsoft.com/sitebuilder/resource/mailfaq.asp
>>> contains important info including how to unsubscribe.  Save time,
>>> search
>>> the archives at http://microsoft.ease.lsoft.com/archives/index.html
>>
>>----------------------------------------------------------------
>>Users Guide http://www.microsoft.com/sitebuilder/resource/mailfaq.asp
>>contains important info including how to unsubscribe.  Save time, search
>>the archives at http://microsoft.ease.lsoft.com/archives/index.html
>>
>>
>
>----------------------------------------------------------------
>Users Guide http://www.microsoft.com/sitebuilder/resource/mailfaq.asp
>contains important info including how to unsubscribe.  Save time, search
>the archives at http://microsoft.ease.lsoft.com/archives/index.html
>

----------------------------------------------------------------
Users Guide http://www.microsoft.com/sitebuilder/resource/mailfaq.asp
contains important info including how to unsubscribe.  Save time, search
the archives at http://microsoft.ease.lsoft.com/archives/index.html

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