Re: mesg Broke on Stable between 8/21 and 8/28

From: horio shoichi (bugsgrief_at_bugsgrief.net)
Date: 08/30/04

  • Next message: Tijl Coosemans: "Re: 4-stable termios diff behaviour lc/lc_r" 
    Date: Mon, 30 Aug 2004 22:52:40 +0900
To: stable@freebsd.org

    On Sun, 29 Aug 2004 18:56:48 -0700
    Dave Tweten <tweten@nas.nasa.gov> wrote:
    > When I replaced a STABLE build from 8/21 with one from 8/29, "mesg"
    > stopped working on xterms.
    >
    > I treat each xterm as a login shell, and include "mesg n" in .login.
    > The problem seems to be that ownership of /dev/ttyp? is not being
    > transferred to the user anymore. I remember that "options UCONSOLE"
    > was involved in the transfer of ownership. That configuration element
    > was in both the 8/21 and 8/28 kernels; nothing was changed in the
    > config file.
    >
    > I checked the mailing list archives, and there does seem to be some
    > recent action in the tty driver area. Unfortunatly, we were
    > compromised recently, and I'm only now getting my connections to e-mail
    > lists (including this one) re-established, so my knowledge of recent
    > list traffic is limited to what I can find on the web site.
    >
    > Does anyone have any idea what has caused the change?
    > --
    > M/S 258-5 |1024-bit PGP fingerprint:|tweten@nas.nasa.gov
    > NASA Ames Research Center| 41 B0 89 0A 8F 94 6C 59| (650) 604-4416
    > Moffett Field, CA 94035 | 7C 80 10 20 25 C7 2F E6|FAX: (650) 604-4377
    > Not an official NASA position; you can't even be certain who sent this!
    >
    >
    > _______________________________________________
    > freebsd-stable@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
    >

    Similar here. On 4.9-STABLE (I'm awaiting ipfilter straightened out).

    The symptoms are:

    o 'mesg n' in .cshrc doesn't cause problem when remotely logged in,

    o starting up with xterm or running script are 'permission denied',

    o vi command 'set nomesg' is 'Operation not permitted'.

    The stem of those problems of mine is recent dropping of setuid bit
    from /usr/X11R6/bin/xterm.

    I tried setting setuid bit on /usr/bin/mesg. It solved the first problem
    but not the second. So, due to the fear of further unforeseen troubles
    (although 'set nomesg' itself doesn't look make much sense),
    I have set setuid back on xterm. Now, it is (they are):

    % ls -aFl /usr/X11R6/bin/xterm*
    lrwxrwxrwx 1 root wheel 27 Aug 30 11:26 /usr/X11R6/bin/xterm@ -> /usr/X11R6/bin/xterm-static
    -rwsr-xr-x 1 root wheel 260792 Aug 29 06:23 /usr/X11R6/bin/xterm-static*
    %

    horio shoichi

    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

  • Next message: Tijl Coosemans: "Re: 4-stable termios diff behaviour lc/lc_r"

    Relevant Pages

    • RE: xscreensaver exploit for Redhat 7.3
      ... On my fresh RH7.3 installation, nothing compiled with that lib is ... There is one major caveat to it though, the setuid application you call ... has to call XtAppInitialize as root. ... The "xterm" example in the ...
      (Vuln-Dev)
    • Re: xscreensaver exploit for Redhat 7.3
      ... There is one major caveat to it though, the setuid application you call ... has to call XtAppInitialize as root. ... The "xterm" example in the ... The "dga" setuid on SuSE 8.0 gives root in a default install, ...
      (Vuln-Dev)
    • Re: mesg Broke on Stable between 8/21 and 8/28
      ... horio shoichi wrote: ... >> stopped working on xterms. ... That configuration element ... > I have set setuid back on xterm. ...
      (freebsd-stable)