RE: RSACryptoServiceProvider() - How to avoid auto key generation
From: Xiao Xie [MSFT] (xiaoxie@online.microsoft.com)
Date: 01/13/03
- Next message: Kim Hellan: "Re: RSACryptoServiceProvider() - How to avoid auto key generation"
- Previous message: Jonathan Clark: "Failure to run from network mapped Drives?"
- In reply to: Kim Hellan: "RSACryptoServiceProvider() - How to avoid auto key generation"
- Next in thread: Kim Hellan: "Re: RSACryptoServiceProvider() - How to avoid auto key generation"
- Reply: Kim Hellan: "Re: RSACryptoServiceProvider() - How to avoid auto key generation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: xiaoxie@online.microsoft.com (Xiao Xie [MSFT]) Date: Mon, 13 Jan 2003 02:51:53 GMT
Kim,
It is by design that the default constructor will always generate a key
pair based on default CspParameters values. You can have constructor to use
predefined keys by using other overloads of the constructor, like:
public RSACryptoServiceProvider(int, CspParameters);
Sincerely,
Xiao Xie
Microsoft Developer Support
This posting is provided "AS IS" with no warranties, and confers no rights.
- Next message: Kim Hellan: "Re: RSACryptoServiceProvider() - How to avoid auto key generation"
- Previous message: Jonathan Clark: "Failure to run from network mapped Drives?"
- In reply to: Kim Hellan: "RSACryptoServiceProvider() - How to avoid auto key generation"
- Next in thread: Kim Hellan: "Re: RSACryptoServiceProvider() - How to avoid auto key generation"
- Reply: Kim Hellan: "Re: RSACryptoServiceProvider() - How to avoid auto key generation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|