RE: Protecting Software (Was: And the plot thickens...)

["Johanson, Roy" <Roy.Johanson@xxxxxxx>]

Mark,

Any EXE or DLL can be protected similar to how some of the TS4 binaries are
protected. If you combine this with a loader or routines that use an in
memory encryption algorithm at runtime, you can probably deter at least 80%
of the people. However, you may also become a target to the elite because of
the challenge and the assumption that there must be some "goodies" hidden in
there to warrant such protection.

http://www.traderhouse.com <http://www.traderhouse.com/targets.htm> 

I have no idea what the cost is for this. 

If the cost is prohibitive or simply do not want to send them your source
code, then a simple compression and run time self-extraction may deter
passive hacking.

http://www.blinkinc.com/ <http://www.blinkinc.com/> 


-- Roy

	-----Original Message-----
	From:	Mark Jurik [SMTP:mark@xxxxxxxxxxxx]
	Sent:	Thursday, February 11, 1999 8:23 PM
	To:	'Patrick White'; omega list
	Subject:	RE: Protecting Software (Was: And the plot
thickens...)

	>> These DLL's could be protected by the same techniques used widely
in the industry. <<

	What are these techniques?  any web sites?

	- Mark


	-----Original Message-----
	From:	Patrick White [SMTP:spy@xxxxxxxxx]
	Sent:	Sunday, February 07, 1999 1:41 PM
	To:	Larry Wright; omega list
	Subject:	Re: Protecting Software (Was: And the plot
thickens...)

	Larry and Omega List,

	I was intrigued by Larry's message that said:

	>It would be *very* easy for developers to make proprietary studies
as
	>DLL's.  Some already do that.  These DLL's could be protected by
the same
	>techniques used widely in the industry. No risk for developers (in
fact,
	>the commercial techniques offer *more* protection than does Omega).


	I'm starting out doing some VB6 programming and am curious about
what kind
	of protection exe files have. I'm wondering if making EXE
applications under
	the VB6 platform offers any kind of protection from hacking or
	disassembling? Are there other (inexpensive) techniques that you
refer to
	that programmers use to protect their works? If so, what might those
be?

	Thanks,

	Patrick White