Path: utzoo!attcan!uunet!decwrl!sdd.hp.com!samsung!umich!yale!cmcl2!panix!alexis From: alexis@panix.uucp (Alexis Rosen) Newsgroups: comp.sys.mac.system Subject: Re: Mac lab security SUMMARY Message-ID: <1990Oct2.063938.5954@panix.uucp> Date: 2 Oct 90 06:39:38 GMT References: Organization: PANIX - Public Access Unix Systems of NY Lines: 34 In the referenced article, jw3z+@andrew.cmu.edu (Judith H. White) writes: >On 26-Sep-90 in Re: Mac lab security SUMMARY >user Alexis Rosen@panix.UUCP 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.) > >You can set the protection to keep applications from being copied from >the server as server administrator. You have to do it on the server >itself, you can't set copy protection from a workstation. > >Just do a get info on the file, and click on the copy protected check >box. It really does work. And the application can still be run. Problem is, this is useless for all but the most inexperienced users, unless you have extremely strict controll over what floppies go in and out of the macs (in which case, you wouldn't need this 'feature' anyway). To Clarify: 1) Hide the app in a folder without "see files" privs. It works, but the app is unavailable. Not useful. 2) Instead, check off the 'copy-protected' box in appleshare. Great. The app works, and the Finder won't copy the file. Trouble is, everything else will. Not useful. This is why lots of other programs, like doppleganger and launchbreaker, were written. (I think I've got the names right. I haven't looked into this in a while.) --- Alexis Rosen {cmcl2,apple}!panix!alexis alexis@panix.uucp