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ü
