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

Message-ID: <20090408190916.0c213aba@lxorguk.ukuu.org.uk>
Date:	Wed, 8 Apr 2009 19:09:16 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Ed Schouten <ed@...eBSD.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Inconsistency between PTY read() return values

On Wed, 8 Apr 2009 19:56:03 +0200
Ed Schouten <ed@...eBSD.org> wrote:

> Hi Alan,
> 
> * Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> > I would argue that TTYs do behave this way. We treat the disconnect as a
> > hang up event. BSD sees it as EOF, Linux as hangup.
> 
> Would you mind explaining me the difference? I thought a modem
> disconnect implies an end-of-file condition? 

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())
--
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/