how to protect my codes

zeeway

unread,

Jun 14, 2006, 10:36:47 PM6/14/06

to

hi,every one!
I have an urgent question. My codes need to be published now,but I learn
programs produced with .net are very easy to be reverse-engineered. Could
anyone give me some sugguestions to protect my c# codes?

Crespo

2006-06-15

CT

unread,

Jun 15, 2006, 12:26:23 AM6/15/06

to

Well, you don't say if it's a Web application, in which situation you're
fairly safe from reverse-engineering. Other issues are related to Web app
security though. If you're releasing a Windows or Console app, then yes it
can be disassembled using various tools. You might want to look into
obfuscation, the process of making disassembling near impossible then.
http://www.microsoft.com/presspass/press/2004/jul04/07-19preemptivesolutionpr.mspx

--
Carsten Thomsen
Communities - http://community.integratedsolutions.dk
---------
Voodoo Programming: Things programmers do that they know shouldn't work but
they try anyway, and which sometimes actually work, such as recompiling
everything. (Karl Lehenbauer)
---------
"zeeway" <zee...@gmail.com> wrote in message
news:O9%23OQSCk...@TK2MSFTNGP03.phx.gbl...

Peter Ritchie

unread,

Jun 16, 2006, 11:53:01 AM6/16/06

to

Obfuscators don't make it "near impossible to disassemble", they just make it
hard to read the disassembled IL. There's nothing stopping someone from
disassembling a native binary as well; it's just harder to map optimized
native code to a specific programming language. The same can be done with
assemblies with a product called Salamander .NET Protector [1] which converts
assemblies from IL to native code; making it as hard to disassemble as
non-managed binaries.

I'm in no way affiliated with RemoteSoft.

[1] http://www.remotesoft.com/salamander/protector.html
--
http://www.peterRitchie.com/

Michael Nemtsev

unread,

Jun 17, 2006, 3:48:37 AM6/17/06

to

Hello zeeway,

I think you should not bother about it if you are not working for the military
or develop some revolutional algorighms
Notwithstanding the fact that you code may be shown it doesn't meen that
it will be understanded by others.
Another fact is that if you provide license for you program you can specify
that scrutinizing the binaries in prohibited

Jon wrote a good article, and I completely argee with his point, related
to the protecting managed code, see it there http://www.yoda.arachsys.com/csharp/obfuscation.html

z> hi,every one!
z> I have an urgent question. My codes need to be published now,but I
z> learn
z> programs produced with .net are very easy to be reverse-engineered.
z> Could
z> anyone give me some sugguestions to protect my c# codes?
z>
z> Crespo
z>
z> 2006-06-15
z>
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

Crespo

unread,

Jul 5, 2006, 10:38:03 PM7/5/06

to

Thank you all your kind advice. Your suggestions are all very useful. And I
would like to know something about ngen.exe. Can this tool be used instead
of Salamander .NET Protector ? Why don't microsoft suppy a tool like
Salamander .NET Protector?

Best Regard
Crespo

"Peter Ritchie" <PRS...@newsgroups.nospam> 写入消息
news:9F6CDF23-9A9A-4A5F...@microsoft.com...

Crespo

unread,

Jul 5, 2006, 10:38:23 PM7/5/06

to

Thank you very much.

"Michael Nemtsev" <nem...@msn.com> ????
news:1799a79b3994a8...@msnews.microsoft.com...