Geek Answers Handbook

Why does RSACryptoServiceProvider.VerifyHash need LDAP verification?

I recently ran into an odd problem RSACryptoServiceProvider.VerifyHash.

I have a web application that uses it to decrypt. When users working with a web service did this through our VPN, it became very slow. When they did not have a connection or an Internet connection, everything was in order.

After searching many times, I found that every time it is called RSACryptoServiceProvider.VerifyHash, it makes an LDAP request for validation MyMachineName\ASPNET.

This does not happen with our WebDev servers (based on cassini), since they work as the current user, and they are really very slow on the VPN, but this should not happen at all.

This seems to be wrong for several reasons:

  • Why does he check the domain controller for the user of the local machine?
  • Why does it bother? Encryption / decryption works independently.

Does anyone know why this is happening or how best to get around this?

+5
source share
2 answers

From this KB, it looks like a “wrinkle” in code that needs to be sorted:

http://support.microsoft.com/kb/948080

+7
source

Thanks (+1 and ans)

Tested and working.

From an article in KB:

SignData VerifyData OID , . . DC, . , OID .

, .

:

rsa.VerifyHash( hashedData, CryptoConfig.MapNameToOID( "SHA1" ), signature );

:

rsa.VerifyHash( hashedData, null, signature );

.

+1

More articles:


All Articles