From: Tom <tom@lemuria.org>
To: kayo <kayo@pyra.ca>
Cc: SELinux@tycho.nsa.gov
Subject: Re: user transparent encryption
Date: Mon, 17 Feb 2003 12:54:00 +0100 [thread overview]
Message-ID: <20030217125359.D3272@lemuria.org> (raw)
In-Reply-To: <1045460612.1408.9.camel@smeagol>; from kayo@pyra.ca on Sun, Feb 16, 2003 at 11:43:32PM -0600
On Sun, Feb 16, 2003 at 11:43:32PM -0600, kayo wrote:
> What I mean in a way creating a situation in which the admin could
> revolk an account or even delete the files but not be able to view the
> encrypted data. Maybe the entire users home directory. Could something
> like this be done at a kernel level. I am toying with the concept of
> absolute privacy for the systems users.
Obviously can't be done. If you do it at the kernel level, the sysadmin
can replace the kernel...
You can STORE data on a remote machine without the admin being able to
read it. Just encrypt it. But as soon as the key needs to be entered on
a machine where you can't trust the admin, it is potentially
compromised.
--
http://web.lemuria.org/pubkey.html
pub 1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
Key fingerprint = C731 64D1 4BCF 4C20 48A4 29B2 BF01 9FA1 2D7A 04F5
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2003-02-17 11:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 2:18 user transparent encryption kayo
2003-02-17 2:43 ` Brian May
2003-02-17 5:43 ` kayo
2003-02-17 8:47 ` Carsten Grohmann
2003-02-17 11:54 ` Tom [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-17 5:40 Joshua Brindle
2003-02-17 7:43 ` Thomas Walcott
2003-02-17 9:18 ` Russell Coker
2003-02-17 15:28 ` w9ya
2003-02-17 15:20 ` Dale Amon
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=20030217125359.D3272@lemuria.org \
--to=tom@lemuria.org \
--cc=SELinux@tycho.nsa.gov \
--cc=kayo@pyra.ca \
/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.