Stolen code

  • Thread starter Thread starter news.microsoft.com
  • Start date Start date
N

news.microsoft.com

Hi,

I have a vb.net 2003 app, that I have given a potential client, and I have a
feeling that they may have taken my stuff and decompiled it, and are now
'building' there own version.

I just used the standard visualstudio.net 2003 build process, and built an
installation project.

Can they reverse the exe into my code, and then just go for it?
 
pretty much...yes.

the obfuscator helps a bit but you can still reverse engineer that...it just
takes a while to make heads/tails of things esp. the larger the
application's code base becomes.

good luck.
 
Yes they can...

There is something call Dotfuscator at gotdotnet (and comes with VS EA 2003)

this will obsfucisication your code. =) I don't know how it works...

-CJ

P.S. I don't think obsfucisication is a real word...
 
steve said:
pretty much...yes.

the obfuscator helps a bit but you can still reverse engineer
that...it just takes a while to make heads/tails of things esp. the
larger the application's code base becomes.

good luck.
Click to expand...

And, as has been said before, even Win32 compiled code can be reverse
engineered. It's just harder. If someone is determined to steal your
code, they will. You just have to make it as difficult as possible.

One suggestion is to put your sensitive code in a standard .DLL or ActiveX
..dll. Not necessarily ideal, but could help.

Anyway, good luck.

Chris
 
Hi CJ,

|| P.S. I don't think obsfucisication is a real word...

I think it must have been through an obfuscisicator - damned if I can work
it out. ;-)

Regards,
Fergus
 
gosh...just the word obfuscation reminds me of the old ms. security addage:

"security through obscurity"

the linux guys would have a field day with the theoretical approach to
dotfuscation!

;^)
 
Yes. Without obfuscation, they have a lot of freedom with your code.
Hopefully, you addressed something like this in your contract with them. You
did have a contract before handing over "sample" code, right?

If your code is unique enough, copyright the code. It will cost a few bucks
and a couple of hardcopies. I would say patent, but that takes too long.
When they come out with their own product, try to get a copy. If it is the
same as the copyrighted code, you may have an option to sue them.

In the interim, once you can prove they screwed you, let the word out to
everyone you know (and you should know a lot of people, as the Internet is a
big place ;->). If they are publicly traded, and you make enough of a stink,
you may get paid after all ... to shut you up!

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

**********************************************************************
Think Outside the Box!
**********************************************************************
 
Fergus Cooney said:
Hi CJ,

|| P.S. I don't think obsfucisication is a real word...

I think it must have been through an obfuscisicator - damned if I can work
it out. ;-)
Click to expand...

hehe =)
 
Cowboy (Gregory A. Beamer) said:
Yes. Without obfuscation, they have a lot of freedom with your code.
Hopefully, you addressed something like this in your contract with them. You
did have a contract before handing over "sample" code, right?

If your code is unique enough, copyright the code. It will cost a few bucks
and a couple of hardcopies. I would say patent,
Click to expand...

That and it usually costs around 15k... =)

but that takes too long.
When they come out with their own product, try to get a copy. If it is the
same as the copyrighted code, you may have an option to sue them.

In the interim, once you can prove they screwed you, let the word out to
everyone you know (and you should know a lot of people, as the Internet is a
big place ;->). If they are publicly traded, and you make enough of a stink,
you may get paid after all ... to shut you up!
Click to expand...

i.e. Blackmail...=)
 
Back
Top