From: Bedros Hanounik <2bedros@gmail.com>
To: reiserfs-list@namesys.com
Subject: trusted processes
Date: Thu, 12 May 2005 17:19:00 -0700 [thread overview]
Message-ID: <f18a8d98050512171937df19c4@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
last year, I asked a question on this list whether we could have file
permissions for programs (or processes) in addition to users and groups. we
need this feature to reject malicious code from accessing system files.
Microsoft has a tech paper about having what they call trusted processes.
you can find it here
http://msdn.microsoft.com/mobility/default.aspx?pull=/library/en-us/dnppcgen/html/wmsecurity.asp
I don't know for how long they've been working on this, but I bet I came up
with this concept first.
what do you think guys of implementing such feature; should it be in the
file system, kernel, or both.
How hard is it to implement, besides the complexity of authentication
management.
-B
[-- Attachment #2: Type: text/html, Size: 898 bytes --]
next reply other threads:[~2005-05-13 0:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 0:19 Bedros Hanounik [this message]
2005-05-13 2:13 ` trusted processes David Masover
2005-05-13 4:05 ` Valdis.Kletnieks
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=f18a8d98050512171937df19c4@mail.gmail.com \
--to=2bedros@gmail.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.