linux-kernel - Re: TTY: tty

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 25 Mar 2012 15:51:43 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Al Viro <viro@...IV.linux.org.uk>
Cc:	Richard Weinberger <richard@....at>, Jiri Slaby <jslaby@...e.cz>,
	linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org,
	Jiri Slaby <jirislaby@...il.com>
Subject: Re: TTY: tty_port questions

On Sat, 24 Mar 2012 23:20:01 +0000
Al Viro <viro@...IV.linux.org.uk> wrote:

> On Mon, Mar 12, 2012 at 11:48:32AM +0000, Alan Cox wrote:
> 
> > > > It will be. In order to fix the tty locking mess we need to shove a lot
> > > > of stuff whose lifetime is the lifetime of the physical port somewhere
> > > > else - the tty_port is that structure.
> > > >
> > > 
> > > "It will be" in terms of "not now"? ;-)
> > 
> > As in, it's the very next step on.
> 
> FWIW, uml console in default config is basically "start xterm for each VC".
> What do you suggest to do on vhangup() on one of those?

What posix says must happen. Which is that the running processes get a
hangup. So a vhangup() would ensure there were no old apps on the UML
guess talking to the xterm (eg stealing login credentials, or abusing
TIOCSTI etc).

The fact it's an xterm isn't really relevant. That's just the physical
interface and vhangup is about breaking the logical link. The xterm would
continue, no reason for it to do otherwise I can see ?

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/