🚀 go-pugleaf

Mitch Kapor's new venture sounded like a neat hack.
Then I read something in MacWorld, March, 1990, MacWorld News, page
119, right under Mitch's picture that chilled my blood. I quote:

	"AppleShare volumes also present a curious problem:
	[On Location] indexes don't respect AppleShare's
	security features, so you can't prevent users from
	finding text in folders they are not authorized to
	read. On Technology plans a fix for a later version."

I administer a medium-size internetwork (8 servers) in an educational
institution. Students have access to the networks. Faculty have access
to the networks. Staff have access. The AppleShare security features
ARE THERE FOR A REASON. We USE the security features.

I now find myself in the extremely uncomfortable position of having to
tell faculty and staff that any work stored on any server must now be
considered available to the public. There is no concievable way to keep
an individule from bringing in a copy of On Location, letting it build
an index, then browse heretofor protected folders to their hearts
content. Many faculty and staff have been keeping mild to very
confidential material safely tucked away on various servers. Faculty
keep exam materials, grades, and answers to the programming labs on the
AppleShare servers.

Gee, THANKS, Mitch. You have just stolen an important amount of
functionality that I HAVE PAID FOR. You have added another layer of
complexity to my job. You are denying me of something that is
rightfully mine. HOW DARE YOU?!?!?

Gee, THANKS, MacWorld. Thanks for blabbing this disasterous situation
out in front of the whole world for anyone to see. Why don't you just
publish the source code to a couple of viruses while you're at it!?

I am NOT a happy camper tonight  :-(

  --scott