Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!ucbvax!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.unix.ultrix
Subject: Re: Ultrix Security Problem
Message-ID: <7094@cbmvax.UUCP>
Date: 15 Jun 89 04:30:30 GMT
References: <7091@cbmvax.UUCP> <622@aurora.AthabascaU.CA>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Organization: Commodore Technology, West Chester, PA
Lines: 22

In article <622@aurora.AthabascaU.CA> lyndon@cs.AthabascaU.CA (Lyndon Nerenberg) writes:
> In article <7091@cbmvax.UUCP> grr@cbmvax.UUCP (George Robbins) writes:
> >
> >Please contact DEC software support to obtain the workaround for this
> >problem, as in most cases, I have no unambiguous way of distinguishing
> >a concerned administrator from an inquisitive cracker.
> 
> Can you give us a bug number or something similar we can use to
> reference this when calling DEC technical support? Trying to describe
> a problem with a description like that usually results in spending
> too many hours on the phone for my liking.-- 

Ah, alas, but to name this particular problem is to make it all to obvious,
and the slip of paper with the bug number is about 2500 miles from here...

If you call DEC and ask about "known security problems" and they play
dumb, I'd be even more upset.   If need be, I'll post the problem number
when I get back to the office, but that's about a week from now.
-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)