From: David Ford <david@blue-labs.org>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Nick LeRoy <nleroy@cs.wisc.edu>,
"Jeffrey W. Baker" <jwbaker@acm.org>,
linux-kernel@vger.kernel.org
Subject: Re: on exit xterm totally wrecks linux 2.4.11 to 2.4.14-pre6 (unkillable processes)
Date: Thu, 01 Nov 2001 22:41:59 -0500 [thread overview]
Message-ID: <3BE21607.2080903@blue-labs.org> (raw)
In-Reply-To: <Pine.LNX.4.33L.0111011839120.447-100000@duckman.distro.conectiva>
You should censor those words ;) You wouldn't want us Americans knowing
about it.
"The <censored> should be fixed."
David
Rik van Riel wrote:
>On Thu, 1 Nov 2001, Nick LeRoy wrote:
>
>>Yeah, I think that I know what I'm talking about. The question
>>was: Should devfs be fixed, or should xterm be fixed.
>>
>
>If any random malicious user can crash the machine through
>devfs, I think the answer to this question is quite obvious.
>
>The security hole should be fixed.
>
>Rik
>
next prev parent reply other threads:[~2001-11-02 3:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-01 16:25 on exit xterm totally wrecks linux 2.4.11 to 2.4.14-pre6 (unkillable processes) Ricardo Martins
2001-11-01 19:05 ` Pierre Rousselet
2001-11-01 19:19 ` Ricardo Martins
2001-11-01 19:31 ` Pierre Rousselet
2001-11-01 19:44 ` Nick LeRoy
2001-11-01 20:00 ` Pierre Rousselet
2001-11-01 20:06 ` Nick LeRoy
2001-11-01 20:13 ` Jeffrey W. Baker
2001-11-01 20:35 ` Nick LeRoy
2001-11-01 20:40 ` Rik van Riel
2001-11-01 21:34 ` Richard Gooch
2001-11-02 3:41 ` David Ford [this message]
2001-11-01 20:42 ` Brian Gerst
2001-11-09 1:17 ` Dr. Kelsey Hudson
2001-11-01 19:47 ` Ricardo Martins
2001-11-01 19:58 ` Per Lidén
-- strict thread matches above, loose matches on Subject: below --
2001-11-02 6:16 Chris Rankin
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=3BE21607.2080903@blue-labs.org \
--to=david@blue-labs.org \
--cc=jwbaker@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nleroy@cs.wisc.edu \
--cc=riel@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.