home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.windows.x:19504 alt.security:4855
- Newsgroups: comp.windows.x,alt.security
- Path: sparky!uunet!mcsun!sun4nl!fwi.uva.nl!casper
- From: casper@fwi.uva.nl (Casper H.S. Dik)
- Subject: Re: /tmp/.X11-unix fileprotection & re-use
- Message-ID: <1992Nov23.222704.573@fwi.uva.nl>
- Keywords: X, security, xinit
- Sender: news@fwi.uva.nl
- Nntp-Posting-Host: adam.fwi.uva.nl
- Organization: FWI, University of Amsterdam
- References: <1992Nov23.202848.18456@riacs.edu>
- Date: Mon, 23 Nov 1992 22:27:04 GMT
- Lines: 26
-
- welch@ames.arc.nasa.gov (Todd Welch) writes:
-
- >In conversations regarding X authorization one item has been
- >suggested having to do with changing protection of /tmp/.X11-unix
- >from its default mode 777 to 700.
-
- >[description of local xhost coercion by usurping DISPLAY elided]
-
- We do something different. First, we have provided startup scripts
- that will default to xauth(1) based Xauthority. Cookies
- are genereated when necessary. If you do that, you no
- longer have to worry about access to the socket.
-
- To prevent removel of the socket, accidental or otherwise,
- we have given the /tmp/.X11-unix directory mode 1777, owner root.
- At that point, Sun's fbtab file comes in handy:
-
- /dev/console 0666 /tmp/.X11-unix/X0
-
- Alternatively, you can put an entry like:
-
- /dev/console 0700 /tmp/.X11-unix
-
- in /etc/fbtab. Mind you, this works only on Sun's running 4.1.x.
-
- Casper
-