Path: utzoo!attcan!uunet!know!samsung!umich!umeecs!msi-s0.msi.umn.edu!cs.umn.edu!ux.acs!clarson
From: clarson@ux.acs.umn.edu (Chaz Larson)
Newsgroups: comp.sys.mac.system
Subject: Re: Mac lab security SUMMARY
Message-ID: <2279@ux.acs.umn.edu>
Date: 26 Sep 90 17:46:50 GMT
References: <8052@milton.u.washington.edu> <10508@panix.UUCP>
Reply-To: clarson@ux.acs.umn.edu (Chaz Larson)
Organization: Iron City, USA
Lines: 34

In article <10508@panix.UUCP> alexis@panix.UUCP (Alexis Rosen) writes:
>As far as I know, the assertion that AppleShare can prevent an
>application from being copied is bogus. (The implication was that
>the app could still be launched. Of course, AppleShare can hide an
>app completely so it can be neither copied nor used.)

From the AppleShare 2.0 Administrator's Guide:

	Using AppleShare Admin, you can copy-protect a file so it can't be
	copied or duplicated in the Finder at a Macintosh workstation.
	(AppleShare's copy-protection feature may have no effect on files
	being used at Apple II or PC workstations.) You copy-protect a file
	in the file information window. Copy-protecting a file does not
	prevent a Macintosh user from opening it and saving it with a
	different name.  Any user can rename, discard, or save changes to a
	copy-protected file or move it somewhere else on the same volume.
	Copy-protection makes the most sense when used with applications 
	whose copyrights or licensing agreements prohibit your making
	copies. Then a Macintosh user can't copy the application to 
	another volume or workstation disk.

I don't know for sure if DiskTop or similar utilities are foiled by this
copy-protection scheme or not.  I don't use this system at the lab; instead
we use LaunchBreak, so if a felonious user copies MS Word and takes it home,
the copy they get is useless outside of the lab.

chaz


-- 
--
       "I Am The Reincarnation of Abraham Lincoln", Insists Prince. 
                 			 -spew
clarson@ux.acs.umn.edu                                       AOL:Crowbone