I'm looking for a fast and secure cryptography algorithm with C# implementation. I need to be able to restore the initial message. What could you suggest?
Thank you for your help!
7
-
1Do you need symmetric or asymmetric encryption?NullUserException– NullUserException2010-08-13 06:20:53 +00:00Commented Aug 13, 2010 at 6:20
-
2It doesn't matter. I need the algorithm to be fast and secure.StuffHappens– StuffHappens2010-08-13 06:27:58 +00:00Commented Aug 13, 2010 at 6:27
-
5There is no such thing as "fast and secure". How fast? Are we talking MBs per second, GBs per second, TBs per second? How secure? Secure against your sister? Secure against your competitors? Secure against government agencies?Damien_The_Unbeliever– Damien_The_Unbeliever2010-08-13 06:34:48 +00:00Commented Aug 13, 2010 at 6:34
-
1Damien has a good point. Your trade-off is performance vs security. The more secure it is, the slower it will be. 256-bit AES is pretty good and I think it's fast enough.NullUserException– NullUserException2010-08-13 06:41:32 +00:00Commented Aug 13, 2010 at 6:41
-
1Actually, StuffHappens is talking about storing key in code - that may not be as secure as he wishes to be regardless of encryption algorithm he choosesVinayC– VinayC2010-08-13 06:58:28 +00:00Commented Aug 13, 2010 at 6:58
|
Show 2 more comments
2 Answers
If you need asymmetric encryption, use 2048-bits RSA.
If you can get away with symmetric encryption, use 256-bit AES.
MSDN Reference:
System.Security.Cryptography
RSACryptoServiceProvider
AesCryptoServiceProvider
You can read about the difference between them here: Symmetric versus Asymmetric.
answered Aug 13, 2010 at 6:21
NullUserException
85.8k31 gold badges212 silver badges239 bronze badges
3 Comments
Nicolas Tyler
Symmetric versus Asymmetric, link is dead. new one here: support.microsoft.com/kb/246071
Henka Programmer
@string.Empty also the new link is dead, here another link good be helpful geeksforgeeks.org/…
Ray
I restored the link to an archived version.
Based on your comments, symmetric encryption should do the trick for you - not to mention it would be faster than asymmetric one. You may want to look at RijndaelManaged class - its same as AES implementation but you have more flexibility in terms of block sizes.
Now, talking about security, it would depend upon how secure is your key. In your case, you are talking about storing it in code. So you need to secure your code/assemblies (say if it is going to lie on controlled server environment). A better option would be to put key in config file (provided config files are stored in controlled environment, they offers flexibility of changing it). In case, you wish to put in code and code/assembly but want to protect from reverse-engineering attacks - obfuscation coupled with Steganography would be way to go. Below are couple of articles on Steganography implementations in .NET:
