linux-kernel - Re: Inconsistency between PTY read() return values

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] [day] [month] [year] [list]

Message-ID: <20090408182255.GJ32098@hoeg.nl>
Date:	Wed, 8 Apr 2009 20:22:55 +0200
From:	Ed Schouten <ed@...eBSD.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Inconsistency between PTY read() return values

* Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> A modem disconnect is a hang up which is quite different to an EOF and is
> effectively a security barrier as well (existing users of the tty port
> lose access to it aka revoke())

Ah, I see. I thought of a hangup as being a physical loss of carrier,
not the method of revoking processes from a TTY. So how come a hangup
can be seen by the pseudo-terminal master? Isn't that something that
should only cause file descriptors to the TTY to become invalid?

-- 
 Ed Schouten <ed@...eBSD.org>

Content of type "application/pgp-signature" skipped