Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!umich!umeecs!msi-s0.msi.umn.edu!cs.umn.edu!kanefsky From: kanefsky@cs.umn.edu (Steve Kanefsky) Newsgroups: comp.sys.mac.system Subject: Re: Mac lab security SUMMARY Message-ID: <1990Sep28.153439.6764@cs.umn.edu> Date: 28 Sep 90 15:34:39 GMT References: Organization: University of Minnesota, Minneapolis - CSCI Dept. Lines: 34 In 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. Take an application that has been copy protected with AppleShare File Server and make a Stuffit archive out of it. Then unstuff the archive somewhere else. Presto! The application has been copied. I'm not trying to tell people how to get around copy protection, I'm just sure that a lot of people know this trick and I don't think AppleShare File Server administrators should have a false sense of security. Like a previous poster mentioned, LaunchBreak is a good way to copy protect applications (and it's free for educational institutions). Users can freely copy applications, but can only use them in the lab where they belong. Until version 2.0 comes out, there are ways around this too, but it requires the thief to have an AppleTalk network and dedicate a machine as a LaunchBreak caterer anywhere he or she wants to use the stolen software. -- Steve Kanefsky kanefsky@cs.umn.edu