linux-kernel - Re: [RFC] potential ancient bug (since 1.99.14) at char/pty

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20091111191609.00c14644@lxorguk.ukuu.org.uk>
Date:	Wed, 11 Nov 2009 19:16:09 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Mauro Carvalho Chehab <mchehab@...hat.com>
Cc:	"Theodore Ts'o" <tytso@....edu>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] potential ancient bug (since 1.99.14) at char/pty

On Wed, 11 Nov 2009 15:01:03 -0200
Mauro Carvalho Chehab <mchehab@...hat.com> wrote:

> Hi Alan/Ts'o,
> 
> There's an open bugzilla at Red Hat for the pty driver that I'm not sure
> what would be the better fix. It tracks to kernel 1.99.14:
> 	http://www.linuxhq.com/kernel/v1.99/13/drivers/char/ChangeLog
> 	http://www.linuxhq.com/kernel/v1.99/13/drivers/char/pty.c

You would need to look at the BSD Unix behaviour and the check SuS v3
specification (which I don't think covers this feature from memory).

I couldn't tell you off hand what the correct behaviour is so you'll have
to do a spot of research
--
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/