Re: .net code security

And with a little skill, reverse engineering most things nowadays (native or
managed) isn't too difficult - native of course more difficult. Noadays..
with common library functions and intelligence built into IDA disassembler -
its getting easier all the time.




-----Original Message-----
From: Discussion of building .NET applications targeted for the Web
[mailto:[email protected]] On Behalf Of Marc Brooks
Sent: Wednesday, January 10, 2007 6:03 PM
To: [email protected]
Subject: Re: [DOTNET-WEB] .net code security

> like that). How does anyone deploy a .net application to production
(public
> use) that has any sort of confidential logic inside of it?

You don't.  Thats the REAL reason Software as a Service matters... to
let you keep all the naughty bits under your control on machines you
own.

If you really care, write your stuff in unmanaged native code,
obsfucate THAT using old-school game stuff and then pInvoke it.  But
even then, there is NO security except physical security.

Your objective should be to make the ownership of your software so
painless, desirable, and reasonable that nobody would think of
stealing it...

--
"I am Dyslexic of Borg. Resistors are fertile. Prepare to have your
ass laminated." -- Dan Nitschke

Marc C. Brooks
http://musingmarc.blogspot.com

===================================
This list is hosted by DevelopMentorR  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com