Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!ucsd!ucbvax!ICARUS.CNS.SYR.EDU!demarsee
From: demarsee@ICARUS.CNS.SYR.EDU (Darryl E. Marsee)
Newsgroups: comp.protocols.appletalk
Subject: Re: Accounting on an AppleShare server?
Message-ID: <8912152130.AA15654@icarus.cns.syr.EDU>
Date: 15 Dec 89 21:30:38 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 29

>##Also, all of our applications have been "Doppleganged" (sp?) with
>##Doppelmaker, so the visible applications are not the actual ones --
>##the actual applications files are invisible -- this keeps the users
>##from copying the applications.
	
>This is not necessary.  There is an option in AppleShare 2.0 to set
>a copy-protect feature on within the Administration utility which prevents
>users from copying the applications.

 I would like to point out that there is a relatively trivial way
 to circumvent AppleShare 2.0's copy-protection system.  Apple has been
 informed of the problem, and hopefully is working on a solution (I 
 have not heard of one yet).  I will say that both Doppleganger and
 Multilauncher, while not alleviating the problem, do make it a bit
 more difficult for a user to circumvent the copy-protection scheme.

 Note:  If you don't know this "relatively trivial way", then don't
        bother asking, I'm not going to tell you.

>To make things simpler, just drop the Doppelganger utility and use
>the built-in features of AppleShare.

 Due to the above-mentioned problem with AppleShare 2.0's copy-protection,
 Noel, I DO NOT recommend that you drop Doppelganger.

 Regards,

 Darryl Marsee <demarsee@icarus.cns.syr.edu>
 Syracuse University Postmaster, TechReper, & MacHacker