🚀 go-pugleaf

Luc Bussieres (bussiere@garrot.DMI.USherb.CA) wrote:
: 
: 	We are in the process of evaluating different network
: alternatives for our students labs. I have installed Borland C++ 3.1
: on an nfs disk, and it is working perfectly. Now I'm trying to find a
: way to restrict the copying of the executable files so that the
: students won't be able to pirate it and to copy it to there home pc. I
: have modify bc.exe with chmodd to execute only, I have try this with
: other executable and it is working correctly. When I do this Borland
: C++ is crashing, it seems that I need to read its own executable. 
: 
: Is there a way to protect Borland C++ from pirating on an nfs disk? 
: 
: Does novell as a copy protection feature that will work with Borland C++?
: 
: Is the only way to protect it is to ask the student to not copy it ?

	The way I would "protect" is restrict WHO can read it.
In Unix you can say a file beongs to the system.
That it's only readable by the system.  But executable by anyone.
That is what you wish to do. 
You could write a daemian that looks for a READ access from it and
checks WHAT WHO issued the request.  IE DOS itself or COPY. 

Unfortunately Unix is much better in the security spectrum than Dos.

(Maybe linux/TCP/IP/X11R5/G++/GCC would be more secure?)

Cyberman


-- 
This is my sig file!
Read rec.games.programer!