- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsI have someone claiming that if he gets a hold of my DLL that makes a SSL call to a web service with username and password, he can decompile the System.io.Stream object and look at my XMLDocument payload and get the login credentials.
How can I protect the code from a decompiler getting my credentials from my XMlDocument payload before I even send my stream over SSL?
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.
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.
Business Accounts
Answer for Membership
by: Omego2KPosted on 2009-10-19 at 09:22:22ID: 25606592
I am guessing he means he could "decompile" the dll and not a specific document. You can easily do this with the IL disassembler that comes with VS. There is no guaranteed way to protect against this. You could however make it so hard to do that no one will waste their time on it. By that I don't mean stop the assembly from being disassembled, but prevent the person from understanding the code. For this you need to use an obfuscator especially with string encryption. A good obfuscator will make code so hard to read that it will take great amounts of time and man power to understand what all the code means. My suggestion for a great and free obfuscator is:
/g1/projec ts/eazfusc ator/dotne t/ Default. aspx
Eazfuscator
located at:
http://www.foss.kharkov.ua