From: viro@parcelfarce.linux.theplanet.co.uk
To: Oliver Tennert <tennert@science-computing.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why Sysrq+k does not offer a trusted path
Date: Mon, 29 Sep 2003 08:21:27 +0100 [thread overview]
Message-ID: <20030929072127.GN7665@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0309290836460.16991-100000@picard.science-computing.de>
On Mon, Sep 29, 2003 at 08:53:59AM +0200, Oliver Tennert wrote:
> Thus it is a more secure way to offer a real SAK.
>
> Or am I missing a very important point?
Scanning through the file descriptor tables of processes does not catch
every opened file out there. For trivial example consider attaching an
open file to SCM_RIGHTS datagram and sending it to yourself. Then close
the original descriptor. Later you will be able to receive the datagram
and get your opened file back.
prev parent reply other threads:[~2003-09-29 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 6:53 Oliver Tennert
2003-09-29 7:20 ` Bernd Eckenfels
2003-09-29 7:21 ` viro [this message]
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=20030929072127.GN7665@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tennert@science-computing.de \
/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
all inboxes | Powered by JetHome®