can a code-behind self-destruct?

[Jason Shohet]

Is there a way for a code-behind to delete the dll after an expiration, or
if a user doesn't enter the right password. ie, lets say i license
something to someone for 3 months. After that time, I want the dll
(representing the c.behind) to become corrupt, or delete itself so it
cannot be hacked by anyone.... Any ideas

 

[Curt_C [MVP]]

2 DLL's, one to check and call the other. Then sure, you could in theory.
But why not just have it not work instead of deletion?

 

[Jason Shohet]

it would prevent hacking the dll... which I assume some people must be able
to do.

 

[Curt_C [MVP]]

If they are smart enough to hack it, they are smart enough to make a copy of
it before it "self destructs".

--
Curt Christianson
Owner/Lead Developer, DF-Software
Site: http://www.Darkfalz.com
Blog: http://blog.Darkfalz.com

 

[Peter Rilling]

Plus, simply deleting it does not make it gone. You can also use one of the
manual file retrieval programs to get it back.

If you don't store any secrets in your application, then there would be
little need to remove it. You can always obfuscate your code before
shipping and strongly name your assemblies.

 

[Jason Shohet]

Thanks to both of you.
can you elaborate on the obfuscation capabilities, or where I can look to
see how to do it. Thats something I haven't looked in to. I'll try to
look up some info on how this is done as well;
When you mention strongly naming assemblies (dll's), are you referring to
the Inherits="...." line in the aspx?

 

[Peter Rilling]

Here is an article on Obfuscation,
http://msdn.microsoft.com/msdnmag/issues/03/11/NetCodeObfuscation/default.aspx.