From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: BUG: bsd pts now climbs continuously
Date: Tue, 10 Aug 2004 04:07:33 +0000 (UTC) [thread overview]
Message-ID: <cf9hm5$tsu$1@terminus.zytor.com> (raw)
In-Reply-To: 1092086245.14770.2.camel@localhost.localdomain
Followup to: <1092086245.14770.2.camel@localhost.localdomain>
By author: Alan Cox <alan@lxorguk.ukuu.org.uk>
In newsgroup: linux.dev.kernel
>
> On Llu, 2004-08-09 at 21:30, jdh wrote:
> > While I'm sure the security issues are valid? I do question completely
> > changing the functionality. I doubt changing the pts/n numbers
> > helps those looking for backward compatibility at all.
>
> ssh breaks at 9999 which is fun too. It runs out of buffer space
> although because its been properly coded it doesn't overrun it just
> starts corrupting utmp
>
This I believe is a glibc bug, and really needs to be fixed.
Unfortunately glibc's handling of utmp is just incredibly broken.
-hpa
next prev parent reply other threads:[~2004-08-10 4:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 20:30 BUG: bsd pts now climbs continuously jdh
2004-08-09 21:17 ` Alan Cox
2004-08-10 4:07 ` H. Peter Anvin [this message]
2004-08-10 11:38 ` Alan Cox
2004-08-10 17:51 ` H. Peter Anvin
2004-08-09 22:48 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='cf9hm5$tsu$1@terminus.zytor.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox