This is a followup question concerning need for "obfuscation" of the code because someone can 'easily' get into and look at the primary code algorithms.
My application deals with highly classified encryption of data and if VB.NET opens up to the whole world what the algorithm is then there is a great problem.
This seems like a VERY GREAT WEAKNESS. I remember now that a few years ago I had decided that this problem was so serious that it kept me from converting to VB.NET. I thought by now that MS would have done something to fix it. Apprently not.
Has anyone run into this problem and does anyone have some sort of solution.
Gary
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Thank you for your information. I have looked at the references and learned from them.
HOWEVER, the question was not about encryption algorithms, I have already done that.
The purpose of my request for information is how do I get around the apparent weakness of
VB.NET with respect to it providing an easy way for others to view the internal methods and
procedures. Is there a way to "obfuscate"? Are there products to do that?
Thanks
garyLittle,
There are products that can be used to make it more difficult to reverse engineer your .NET assemblies, but it's impossible to protect them completely. Anyone who is prepared to invest the effort will be able to disassemble your code and eventually reconstruct your algorithms.
One of the best known products is Dotfuscator ( http://www.preemptive.com/
In your case, as I pointed out, it shouldn't matter if someone can see your encryption algorithms. As long as you have chosen a good encryption method and exercise good control of your encryption keys it should not be possible for someone to break your codes even with knowledge of how they were enciphered. As for your general algorithms, I'm afraid that there is no bulletproof way to hide them from prying eyes, so if you do come up with a killer app make sure that you patent it so that you will have some legal recourse when it gets stolen.
Business Accounts
Answer for Membership
by: KelvinYPosted on 2006-09-13 at 12:25:58ID: 17514901
Hi garyLittle,
I'm not sure where you get the idea that exposing an encryption algorithm is a weakness. The best encryption algortihms are the one's that have been extensively studdied and proven to have no obvious weaknesses. The only thing that needs to be secure is the encryption key. This a well-known principle - http://en.wikipedia.org/wi
If you are using .NET then you have access to some very secure algorithms in the System.Security.Cryptograp
Regards
Kelvin