By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
458,122 Members | 1,615 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 458,122 IT Pros & Developers. It's quick & easy.

Protecting Assembly against disassembling...

P: n/a
Hi,
how can i protect a assembly against disassembling with ILDASM and
other products like that. i have a dll with some encryption methods
implemented and i dont want them to be exposed, to the outside of
the world. of cource there are restrictions like modifiers and misc.
but i dont want the assembly "disassembled" from someone with
"bad intentions"...

How can i protect it efficiently...?

Thanks in advance
Kerem Gümrükcü
Jul 21 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Kerem,

Look in this newsgroup what is written about obfucator,
When that is not enough you can as well look in the newsgroups
microsoft.visual.basic.languages.vb and csharp, than you get a multiple of
these answers.

http://groups-beta.google.com/group/...rch+this+group

I hope this helps,

Cor
Jul 21 '05 #2

P: n/a
Use the CryptoAPI for your encryption needs and use modern encryption
techniques that don't place the key into the code.

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"Kerem Gümrükcü" <ka*******@hotmail.com> wrote in message
news:eD**************@TK2MSFTNGP09.phx.gbl...
Hi,
how can i protect a assembly against disassembling with ILDASM and
other products like that. i have a dll with some encryption methods
implemented and i dont want them to be exposed, to the outside of
the world. of cource there are restrictions like modifiers and misc.
but i dont want the assembly "disassembled" from someone with
"bad intentions"...

How can i protect it efficiently...?

Thanks in advance
Kerem Gümrükcü

Jul 21 '05 #3

P: n/a
Hi,

i dont place any keys inside my code, this would be stupid and foolish.
key and/or iv are placed in memory and you cant avoid this!
The point is to protect my code against disassembling with ldasm and
other stuff. but the major part of the code has already been rewritten
to cpp...we cant use microsofts crypto api, because the code must be
portable to other plattforms like mono-project or ansi c++ compilers...
Regards
Kerem Gümrükcü
Jul 21 '05 #4

P: n/a
Sorry for the misunderstanding. Your original post appeared to say that the
reason you wanted to avoid ildasm was to prevent exposure of your encryption
methods. Most encryption/decryption code is public knowledge and often open
source, (all the most secure ones are, anyway), so I was assuming that you
had rolled your own encryption method and that your code wasn't
sophisticated, and that you were concerned enough to hide it.

It appears that I misread your original post.

Note: there still has to be a key somewhere. It's either in your code or
it's not. If it is not, that is better. Since you were so concerned about
ILDASM, I assumed that it was in your code. Your follow-up statement is
intriguing. If you have found a way to encrypt and decrypt securely without
using a private or symmetric key that has to be stored somewhere, I'd love
to hear about it.

If your app has been rewritten to cpp this quickly, then this discussion
(about ILDASM) is moot. C++ is a fine language and runs well on many
different platforms.

Good Luck.

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"Kerem Gümrükcü" <ka*******@hotmail.com> wrote in message
news:Os**************@tk2msftngp13.phx.gbl...
Hi,

i dont place any keys inside my code, this would be stupid and foolish.
key and/or iv are placed in memory and you cant avoid this!
The point is to protect my code against disassembling with ldasm and
other stuff. but the major part of the code has already been rewritten
to cpp...we cant use microsofts crypto api, because the code must be
portable to other plattforms like mono-project or ansi c++ compilers...
Regards
Kerem Gümrükcü

Jul 21 '05 #5

P: n/a
Try to use Spices.Net Obfuscator (http://spices.9rays.net) with antiILDASM =
True or Complete to prevent your assembly from opening and full
disassembling by ILDASM.
Also usage of this option crashes some decompilers.

--
Best regards,
Al Ponomarev

Jul 21 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.