From: Jan Petranek <jan@petranek.de>
To: selinux@tycho.nsa.gov
Subject: Goal / Danger: Attack by malicious root
Date: Mon, 15 Jan 2001 16:08:34 +0100 [thread overview]
Message-ID: <01011516091701.13938@linux16> (raw)
dear guys,
did You consider the possibility of an malicious root attacks? In most
Linuxdistributions, the priviliged user can read & manipulate all of the user's
data.
This is indeed a situation I find myself in today: I am working on a
Linux-Machine in the university's computer pool. And I find my own
(non-encrypted) home directory far too insecure to put a private key or
something like that in here. This is also from the point of view, that the
root-login may be hacked on a campus site like this.
So to me, there is a need of encrypting the user's data. The question of the
key yet remains: A key like a password / passphrase is quite limited in it's
length (by the memory of the user). A key on a medium (like a CD-ROM,
chipcard etc.) could be longer, but still there is the demand, that it can't be read by
somebody else (not even the superuser), when mounted /
used by the user.
Also, the key medium could compromise the encryption, but that is another
problem.
I'd be quite glad, if you could take this point in consideration,
JanP
--
You have received this message because you are subscribed to the selinux 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 reply other threads:[~2001-01-15 15:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-15 15:08 Jan Petranek [this message]
2001-01-15 13:02 ` Goal / Danger: Attack by malicious root Robert Hartley
2001-01-15 16:22 ` Bennett Todd
2001-01-15 16:52 ` Andi Kleen
2001-01-15 16:45 ` Preston L. Bannister
2001-01-15 17:53 ` Johnathon Day
2001-01-15 19:19 ` Bennett Todd
2001-01-15 21:18 ` Johnathon Day
2001-01-16 9:22 ` Matthew Pemble
2001-01-16 12:53 ` Stephen Smalley
-- strict thread matches above, loose matches on Subject: below --
2001-01-16 12:28 Roger
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=01011516091701.13938@linux16 \
--to=jan@petranek.de \
--cc=selinux@tycho.nsa.gov \
/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.