Take the 2-minute tour ×
Information Security Stack Exchange is a question and answer site for Information security professionals. It's 100% free, no registration required.

This question already has an answer here:

I created one software which written in c#.net and when i created setup file .exe file will be the output but in this .exe file is ex tractable by some software and easy to access the codes.How to prevent this?

share|improve this question
    
Although this answer was marked as a duplicate w.r.t. DRM, I think this answer may assist you: Look at SLP, formerly from Microsoft security.stackexchange.com/a/1091/396 –  makerofthings7 Jun 29 '13 at 18:45
add comment

marked as duplicate by TildalWave, Adnan, Polynomial, Xander, NULLZ Jun 29 '13 at 13:37

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

2 Answers

up vote 3 down vote accepted

No matter what you do, no matter what you use, somebody will be able to extract/infer the source code of your application from the binary. There's just no way around it. In the worst case they can run the application through a debugger and with assembly knowledge it could be possible to infer the source code.

Having that said, there are many good obfuscatory for .Net. They make it a bit more difficult to extract the source code from the binary. Here's a list of some of them on Wikipedia.

share|improve this answer
    
Funny I don't see SLP on that list... inishtech.com –  makerofthings7 Jun 29 '13 at 18:46
    
@makerofthings7 No disrespect, but this is Wikipedia. If there's something missing or you see something you can improve, then add it yourself instead of complaining about it. –  Adnan Jun 29 '13 at 20:25
    
None taken. Also I'm not complaining... The omission makes me question market awareness whenever I would be required to make a product listing, especially when it's a former MSFT product. Maybe there is something unpopular/undesirable with the product I don't know of. That is where I was phishing for information ;) –  makerofthings7 Jun 29 '13 at 20:48
add comment

You could run your project through an obsfucator tool like Eazfuscator.NET.

This should make it a lot more difficult to recover the original source code given the .NET binary file. Of course, this is not 100% foolproof. With enough time and effort, an attacker would probably have a high chance of deobsfucating the binary file.

share|improve this answer
    
its minimum requirement is .NET 4.0 but i am using .NET 3.5 –  Suresh E Jun 29 '13 at 11:51
1  
@SureshE Search around for other obsfucator tools. There are plenty available out there. –  Terry Chia Jun 29 '13 at 11:52
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.