From: Andries Brouwer <Andries.Brouwer@cwi.nl>
To: Bodo Eggert <7eggert@gmx.de>
Cc: Andries Brouwer <Andries.Brouwer@cwi.nl>,
linux-kernel@vger.kernel.org, akpm@osdl.org, horms@verge.net.au
Subject: Re: security / kbd
Date: Sat, 3 Dec 2005 03:39:46 +0100 [thread overview]
Message-ID: <20051203023946.GC24760@apps.cwi.nl> (raw)
In-Reply-To: <Pine.LNX.4.58.0512030251570.6039@be1.lrz>
On Sat, Dec 03, 2005 at 03:11:42AM +0100, Bodo Eggert wrote:
> On Sat, 3 Dec 2005, Andries Brouwer wrote:
> > Didnt I show a "bleeding edge" patch some April 1st or so?
>
> It's a bad day for presenting a useful patch.
Hardly useful. Somewhat funny. I just looked - it was April 1st, 2002.
> > Let me repeat what I said and you snipped:
> > If there is a security problem, then it should be solved in user space.
>
> By killing and disabeling all remote logins when root logs in or by
> ptracing each user program during root sessions? You'd have to do this
> until we find somebody to do the correct fix in the kernel.
Please describe the perceived security problem.
I see words, but no problem.
You log in remotely to my machine. Want to do something evil.
What precisely do you do?
2.0.34% loadkeys -d
Couldnt get a file descriptor referring to the console
How do you propose this remotely logged-in non-root gets access to
a console file descriptor?
Andries
next prev parent reply other threads:[~2005-12-03 2:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5f6Fp-1ZB-11@gated-at.bofh.it>
2005-12-03 0:21 ` security / kbd Bodo Eggert
2005-12-03 1:34 ` Andries Brouwer
2005-12-03 2:11 ` Bodo Eggert
2005-12-03 2:39 ` Andries Brouwer [this message]
2005-12-03 5:33 ` Bodo Eggert
2005-12-03 14:46 ` Andries Brouwer
2005-12-03 17:19 ` Bodo Eggert
2005-12-03 18:11 ` Andries Brouwer
2005-12-03 18:48 ` Bodo Eggert
2005-12-03 21:43 ` Andries Brouwer
2005-12-02 0:08 Andries Brouwer
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=20051203023946.GC24760@apps.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=7eggert@gmx.de \
--cc=akpm@osdl.org \
--cc=horms@verge.net.au \
--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 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.