RSA CryptoAPI storage bin problem(?)

[Greg Merideth]

I've finally got my client/server secure soap process working and I've
just noticed that under the servers
[base]\NetworkService\App[..]Data\MS\Crypto\RSA folder there are some
100+ paired sets of RSA keys.

I don't setup RSACryptoServiceProvider using CspParameters and I didn't
give the RSA initiator any paramters when I setup the class yet, each
implementation of the RSA class, as a web service, is creating a
cryptoAPI storage bin for the RSA public/private key. There's literally
100's of them in there from testing.

Was there a change with beta 2 or .net 1.1 where creating an RSA key
automatically stores the keys in the (in this case) networkservice
crypto storage bin or do you have to specifically tell the RSA class not
to store the generated keys?

The local command line client "caller" test program creates two
RSACryptoServiceProvider's yet it doesn't store the public keys anywhere
on the local machine, this seem's to happen just to the web service.

This is being done from vs 2003 to a win 2k3 machine running .net 1.1.

Thanks for any help.

 

[Greg Merideth]

I forgot to mention that I also set PersistKeyInCsp to false when I
create the RSACryptoServiceProvider class.