From: Hans Reiser <reiser@namesys.com>
To: Reiserfs mail-list <Reiserfs-List@Namesys.COM>,
Reiserfs mail-list <Reiserfs-List@Namesys.COM>
Subject: request for comments, proposal to isolate processes using views for greater security
Date: Thu, 15 Jan 2004 04:13:46 +0300 [thread overview]
Message-ID: <4005E94A.6060402@namesys.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 381 bytes --]
this proposal is due 6am EST on the 15th, so I have just enough time for
a few more tweaks after I wake up tomorrow.....
It occurred to me that maybe others might also find it interesting to
sponsor.... I really think that this could be used to make Linux
distributions a lot more secure, especially if applied to every process
that accepts remote connections....
--
Hans
next reply other threads:[~2004-01-15 1:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 1:13 Hans Reiser [this message]
2004-01-15 1:48 ` request for comments, proposal to isolate processes using views for greater security Jason Holt
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=4005E94A.6060402@namesys.com \
--to=reiser@namesys.com \
--cc=Reiserfs-List@Namesys.COM \
/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.