home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!zaphod.mps.ohio-state.edu!uwm.edu!psuvax1!rutgers!flop.ENGR.ORST.EDU!xanth.CS.ORST.EDU!villalj
- From: villalj@xanth.CS.ORST.EDU (John Villalovos)
- Newsgroups: bit.listserv.novell
- Subject: Re: Re: Copying protected software
- Message-ID: <1ht7oiINNq1h@flop.ENGR.ORST.EDU>
- Date: 30 Dec 92 22:27:30 GMT
- References: <9212301553.AA04281@GoldnG8.univnorthco.edu>
- Organization: Oregon State University
- Lines: 21
- NNTP-Posting-Host: xanth.cs.orst.edu
-
- In article <9212301553.AA04281@GoldnG8.univnorthco.edu> Novell LAN Interest Group <NOVELL@SUVM.BITNET> writes:
- >It appears as if there isn't any good way to keep someone from copying
- >software from a server, doesn't it? One comment that you let only trusted
- >users on the network is a good idea, but can't be done in a student lab
- >environment.
- >
- >Another way to maybe stop un-sophisticated users is to call the executable
- >from another (using a utility like ANY/PATCHANY that comes with NETLOCK)
- >so that it appears to be the actual executable but is not. Maybe the
- >exe could even be renamed and flagged hidden????
- >
- Also if you are using a program like Lanlock which takes the EXE file and adds
- a loader module to the code it will not run once the program is taken off the
- network.
-
- Later,
- --
- John Villalovos
- Certified Netware Engineer
- villalj@xanth.cs.orst.edu
- (503) 753-7883
-