Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!jarthur!uci-ics!gateway From: truesdel@ICS.UCI.EDU (Scott Truesdell) Newsgroups: comp.sys.mac Subject: Re: On Location is BAD NEWS! Message-ID: <11545.635496974@ics.uci.edu> Date: 20 Feb 90 07:01:09 GMT Lines: 42 ------- Forwarded Message Received: from gateway.qm.apple.com by goofy.apple.com (5.51/25-eef) id AA02895; Mon, 19 Feb 90 12:54:01 PST for truesdel@ics.uci.edu Message-Id: <9002192054.AA02895@internal.apple.com> Date: 19 Feb 90 12:03:39 From: Tom Dowdy Subject: AppleShare and On Location To: truesdel@ICS.UCI.EDU Snausages! From the office of Tom Dowdy Regarding: AppleShare and On Location Okay. I just got a call back from one of the main AFP folks. There is *no* way that On Location could be getting around the AppleShare file mechanisms, and your server is perfectly save. AFP has no "block read" type primative, so there isn't any way that a program can get to a file they aren't allowed to have. As I stated before, if the admin runs an On Location index on the server and then places that index in a public place, or if a user does the same for those files s/he has access to, this can cause a problem. The answer to this is "don't do that" and you shouldn't have any problem. You can post this to the net if you like, or I will. Just wanted to get back to you as soon as possible with a more concrete answer. Tom Dowdy Internet: dowdy@apple.COM Apple Computer MS:81EQ UUCP: {sun,voder,amdahl,decwrl}!apple!dowdy 20525 Mariani Ave AppleLink: DOWDY1 Cupertino, CA 95014 "The 'Ooh-Ah' Bird is so called because it lays square eggs." ------- End of Forwarded Message Thank you, Tom. This looks like a more manageable problem now. --scott