From: David Maynor <david.maynor@oit.gatech.edu>
To: linux-kernel@vger.kernel.org
Date: Tue, 07 Aug 2001 13:43:58 -0400 [thread overview]
Message-ID: <5.1.0.14.2.20010807133852.00a8ed90@pop.prism.gatech.edu> (raw)
>What you are saying above suspiciously sounds like:
>
> "I want an onion, lets leave out the layers!"
>
>If you really want an onion, I suspect encrypted
>swap will be a useful layer to have as part of your
>onion...
>
>Rik
Not at all, I am saying if you are worried about such things, then start
with projects that would not require a hardware crypto card to make i
useable. I thought this was focusing on keeping laptops secure, and I don't
know anybody that makes a crypto co-processor in the pcmcia variety. There
are things you can do to harden the kernel against such things with out
encrypting everything is site. My view on encryption is like chocolate, its
good, to much will make you sick.......
reply other threads:[~2001-08-07 17:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5.1.0.14.2.20010807133852.00a8ed90@pop.prism.gatech.edu \
--to=david.maynor@oit.gatech.edu \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®