Hi, I am trying to port an existing PC application to a particular
handheld device that runs WinCE 5.0 and .NetCF 2.0 SP1. The
application uses DSA signatures to interface with an existing body of
applications.
The following code lines that work fine on WinXP:
DSACryptoServiceProvider DSA = new
DSACryptoServiceProvider();
DSA.ImportParameters(DSAp);
blow up on the handheld:
System.Security.Cryptography.CryptographicException was unhandled
Message="CryptoAPI cryptographic service provider (CSP) for this
implementation could not be acquired."
StackTrace:
at System.Security.Cryptography.Utils._AcquireCSP()
at System.Security.Cryptography.Utils.AcquireProvHandle()
at System.Security.Cryptography.Utils.get_StaticDssProvHandle()
at
System.Security.Cryptography.DSACryptoServiceProvider.ImportParameters
()
at xxxx.Form1.bVerify_Click()
Google research shows that this commonly occurs on ASP and other web
services where the web applications does not have proper access to the
key store (a file under Documents and Settings...). Following these
posts, I have tried setting UseMachineKeyStore, and even creating the
"Documents and Settings" tree on the handheld, with no success. I
have not found any mention of this bug in connection with Windows CE,
Pocket PC or .NetCF. And there does not seem to be anything like
FileMon or RegMon for the handheld.
Can anyone explain what WinCE is looking for when it tries to
"acquire" a CSP, or how I can work around this exception?
Thanks,
Larry
P.S. My first thread on this subject was in an encryption group
("Please help: DSAParameters in Security",
microsoft.public.platformsdk.security). It now looks like a CE
platform problem, since I have the same problem on my IPAQ (Pocket PC
2003).
|
Similar Threads
