How to protect a dll

[Peter]

I wrote a dll and now I want to protect from mass distribution. What
is the most COST software for doing this, or can it easily be done in
vb.net.

[Herfried K. Wagner [MVP]]

* pe***@mclinn.co m (Peter) scripsit:

I wrote a dll and now I want to protect from mass distribution. What
is the most COST software for doing this, or can it easily be done in
vb.net.

That's possible "out of the box":

<URL:http://msdn.microsoft. com/library/en-us/cpguide/html/cpconlicensingc omponentscontro ls.asp>
<URL:http://windowsforms.ne t/articles/Licensing.aspx>

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Howard Kaikow]

I don't see how that protects the code.
Cannot one can still decompile and defeat the code that using the licensing
components listed below?

--
http://www.standards.com/; See Howard Kaikow's web site.
"Herfried K. Wagner [MVP]" <hi************ ***@gmx.at> wrote in message
news:2g******** ****@uni-berlin.de...

* pe***@mclinn.co m (Peter) scripsit:

I wrote a dll and now I want to protect from mass distribution. What
is the most COST software for doing this, or can it easily be done in
vb.net.
That's possible "out of the box":

<URL:http://msdn.microsoft.com/library/en...nlicensingcomp
onentscontrols. asp> <URL:http://windowsforms.ne t/articles/Licensing.aspx>

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Herfried K. Wagner [MVP]]

* "Howard Kaikow" <ka****@standar ds.com> scripsit:

I don't see how that protects the code.
Cannot one can still decompile and defeat the code that using the licensing
components listed below?

I didn't yet play around with them, but I think additional obfuscation
may be the way to go.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Howard Kaikow]

Obfuscation just makes the task of decompiling harder.
In addition, using obfuscation adds another, needless, element that could
botch up a project.
What if the obfuscator screws up things?
It's hard enough to debug as is without having to worry about problems
caused by obfuscation.

Not to mention, using the built-in, or another commercially available,
obfuscator, means that those obfuscators are likely to be targeted and
cracked at some point, if not already.
--
http://www.standards.com/; See Howard Kaikow's web site.
"Herfried K. Wagner [MVP]" <hi************ ***@gmx.at> wrote in message
news:2g******** ****@uni-berlin.de...

* "Howard Kaikow" <ka****@standar ds.com> scripsit:

I don't see how that protects the code.
Cannot one can still decompile and defeat the code that using the licensing components listed below?

I didn't yet play around with them, but I think additional obfuscation
may be the way to go.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Herfried K. Wagner [MVP]]

* "Howard Kaikow" <ka****@standar ds.com> scripsit:

Obfuscation just makes the task of decompiling harder.
In addition, using obfuscation adds another, needless, element that could
botch up a project.
What if the obfuscator screws up things?
Depends on the obfuscator. There are AFAIK obfuscators available that
do not break reflection, for example.
Not to mention, using the built-in, or another commercially available,
obfuscator, means that those obfuscators are likely to be targeted and
cracked at some point, if not already.

I think there is big difference to what we had in VB6 or C. If the
algorithm itself should be protected, don't put it onto the
client. Provide a web service or something like that on a separate
server.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Howard Kaikow]

In the real world, most apps run locally, not over a web.

--
http://www.standards.com/; See Howard Kaikow's web site.
"Herfried K. Wagner [MVP]" <hi************ ***@gmx.at> wrote in message
news:2g******** ****@uni-berlin.de...

* "Howard Kaikow" <ka****@standar ds.com> scripsit:

Obfuscation just makes the task of decompiling harder.
In addition, using obfuscation adds another, needless, element that could botch up a project.
What if the obfuscator screws up things?

Depends on the obfuscator. There are AFAIK obfuscators available that
do not break reflection, for example.

Not to mention, using the built-in, or another commercially available,
obfuscator, means that those obfuscators are likely to be targeted and
cracked at some point, if not already.

I think there is big difference to what we had in VB6 or C. If the
algorithm itself should be protected, don't put it onto the
client. Provide a web service or something like that on a separate
server.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Herfried K. Wagner [MVP]]

* "Howard Kaikow" <ka****@standar ds.com> scripsit:

In the real world, most apps run locally, not over a web.

In real world, 99,99 percent of the users do not want the source code
and do not decompile the application.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Doknjas]

>

I didn't yet play around with them, but I think additional obfuscation may be the way to go.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

Obfuscation will help protect your intellectual property, but it won't
prevent someone from distributing the latest version of your software
free. All they have to do is decompile, and step through one line at
a time to remove license checks or other checks, and presto - free
code.

The ability to decompile and step through line-by-line will always
ensure that anyone who wants your software without paying will have
it without paying.

[Cor Ligthert]

> Obfuscation will help protect your intellectual property, but it won't

prevent someone from distributing the latest version of your software
free. All they have to do is decompile, and step through one line at
a time to remove license checks or other checks, and presto - free
code.

The ability to decompile and step through line-by-line will always
ensure that anyone who wants your software without paying will have
it without paying.

However in my country there is a law, that when you steal a car, the car is
still be stolen when you repaint it. However maybe that is not everywhere
the same.

Cor