pkg/47713: emacs 23.4 still relies on old-style pty device nodes

[he%NetBSD.org@localhost]

>Number:         47713
>Category:       pkg
>Synopsis:       emacs 23.4 still relies on old-style pty device nodes
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Apr 03 15:45:01 +0000 2013
>Originator:     Havard Eidnes
>Release:        NetBSD 6.1_RC2
>Organization:
        None.
>Environment:
System: NetBSD smistad.uninett.no 6.1_RC2 NetBSD 6.1_RC2 (MAANEN) #0: Wed Mar 
27 23:04:34 CET 2013 
he%smistad.uninett.no@localhost:/usr/obj/sys/arch/i386/compile/MAANEN i386
Architecture: i386
Machine: i386
>Description:
        Emacs 23.4nb10 still needs the old-style pty device nodes to
        properly run sub-processes with ttys.

        One example is the "shell" mode.

        One other example is that mail/mew's pgp (or gpg) signing
        doesn't work unless the old-style pty device nodes are there,
        as it otherwise complains (from ktrace):

       "[GNUPG:] NEED_PASSPHRASE B7E1EBC69ADF790B B7E1EBC69ADF790B 17 0\n"
...
 15599      1 gpg      GIO   fd 2 wrote 5 bytes
       "gpg: "
 15599      1 gpg      RET   write 5
 15599      1 gpg      CALL  write(2,0xbfbfdca4,0x32)
 15599      1 gpg      GIO   fd 2 wrote 50 bytes
       "cannot open tty `/dev/tty': Device not configured\n"
 15599      1 gpg      RET   write 50/0x32
...

        The old-style pty nodes are evidently a security risk if you
        also have ptyfs mounted (which I have) -- re-creating the
        old-style device nodes to fix this problem gives this warning:

# sh MAKEDEV pty0
MAKEDEV: pty0: creating BSD style tty nodes with ptyfs is a security issue
# sh MAKEDEV pty1
MAKEDEV: pty1: creating BSD style tty nodes with ptyfs is a security issue
#

        ...so a better solution should be found.
        It does however work around the problem.

>How-To-Repeat:
        Use editors/emacs, try to do M-x shell, with either tcsh or
        csh as your shell, and see it complain about access to the pty
        and therefore no job control (I only tested with tcsh).

>Fix:
        Yes, please. :)