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

Thanks....

P: n/a
Thanks for all the answers and ideas, but i think the best thing i can do
is to rewrite the dll in c++ to make it difficult to read. of course this
wont stop a experienced assembler coder, but for the rest of the word
this is the best solution i think....

thanks again...
Kerem Gümrükcü
Nov 16 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Just use an obfuscator to obfuscate the code, if anything really.
Anyone able to break that has probably spent more time understanding and
then recreate that highly cryptical code
than he would have done writing it from scratch, which he/she might well be
able to do.
Not to mention drawbacks like maintenance in a system you really do not
know,
and the potentially awkward situations when customers asks technological
questions about the software...

Finding and stealing special code parts may be quite easy to do,
but stealing the functionality of an entire application, and then make use
of it commercially, is IMO very difficult, more or less depending on the
extent of the application.
--
Regards,
Dennis JD Myrén
Oslo Kodebureau
"Kerem Gümrükcü" <ka*******@hotmail.com> wrote in message
news:u5**************@TK2MSFTNGP09.phx.gbl...
Thanks for all the answers and ideas, but i think the best thing i can do
is to rewrite the dll in c++ to make it difficult to read. of course this
wont stop a experienced assembler coder, but for the rest of the word
this is the best solution i think....

thanks again...
Kerem Gümrükcü

Nov 16 '05 #2

P: n/a
It's your money.

--
--- 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:u5**************@TK2MSFTNGP09.phx.gbl...
Thanks for all the answers and ideas, but i think the best thing i can do
is to rewrite the dll in c++ to make it difficult to read. of course this
wont stop a experienced assembler coder, but for the rest of the word
this is the best solution i think....

thanks again...
Kerem Gümrükcü

Nov 16 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.