Path: utzoo!attcan!uunet!husc6!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: X11R3 security hole needs attention
Message-ID: <8903201249.AA21044@EXPIRE.LCS.MIT.EDU>
Date: 20 Mar 89 12:49:09 GMT
References: <8903172239.AA00594@buit5.bu.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 16


    Is there anything we can do to alleviate the problem?

You could convince BU to join the X Consortium; you could convince BU to
invoke corrective feedback on deviant behavior; you could convince BU to pay
someone to implement a solution.  Since I have no real idea what your
environment is (e.g. whether you are also running product servers, have X
terminals, are running product applications, etc.) and what level of security
you want, it's rather difficult to say what will alleviate the problem.

    If there is no way to handle this, I am going to recommend to my superiors
    that we support Suntools and get out of the X situation entirely.

This situtation has existed since the beginning of (X) time; your students are
suddenly catching on (I thought they'd be better than that :-), and you're
suddenly in a do-or-die situation?