From: Dustin Reyes <crusader@linuxgames.com>
To: selinux@tycho.nsa.gov
Subject: Crypto FS
Date: Thu, 8 Feb 2001 15:53:29 -0600 [thread overview]
Message-ID: <20010208155329.A1383@linuxgames.com> (raw)
Re: Integrate existing publicly available file cryptography
with file mandatory controls
Will the SE Linux team (NAI Labs, NSA, etc.) be conducting
an extensive security audit of current Linux disk encryption?
I'm asking this question from more of a legal viewpoint,
due to the Executive branch of the federal government's
traditional negative stance towards *effective* personal data
encryption without key escrow as it interferes with
law enforcement to some degree.
I know that the team hopes that the philosophy behind SE Linux's
architecture and SE Linux itself become a standard in
the industry, but will the strength of fs crypto be compromised,
or not examined with the same rigor, as the rest of the
distribution/system?
It may not be a legal problem per se, but I'm concerned that NSA
culture and tradition would prevent a thorough analysis (and the
release of solutions or enhancements to any problems)...
Finally, I'm not a professional coder or cryptologist, so this question
may be completely invalidated by encrypted filesystems are
already implemented... if so, I apologize in advance.
Thanks for your patience and time.
-Dustin
--
Dustin Reyes - crusader@linuxgames.com
LinuxGames - http://www.linuxgames.com
--
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-02-08 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 21:53 Dustin Reyes [this message]
2001-02-08 21:56 ` Crypto FS Dustin Reyes
2001-02-09 13:19 ` Dale Amon
-- strict thread matches above, loose matches on Subject: below --
2001-02-09 22:04 Pete Loscocco
2001-02-10 0:29 ` Sandy Harris
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=20010208155329.A1383@linuxgames.com \
--to=crusader@linuxgames.com \
--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.