From: Hans Reiser <reiser@namesys.com>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Brett Russ <icycle@charter.net>,
Reiserfs-List <reiserfs-list@namesys.com>
Subject: Re: Behavior of tails with respect to shred, wipe, etc
Date: Sat, 26 Oct 2002 05:41:10 +0400 [thread overview]
Message-ID: <3DB9F2B6.6000701@namesys.com> (raw)
In-Reply-To: 15801.26994.705639.374241@laputa.namesys.com
Nikita Danilov wrote:
>
>I guess we should address this issue in reiser4. This is -security-
>feature after all. Hans? It is not clear how to intehgrate this with
>journalling though.
>
> >
>
>Nikita.
>
>
>
>
Use encryption. Encryption still leaves you vulnerable to those who can
extract the key out of the owner though.
Hans
next prev parent reply other threads:[~2002-10-26 1:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 15:40 Behavior of tails with respect to shred, wipe, etc Brett Russ
2002-10-25 15:55 ` Nikita Danilov
2002-10-25 16:00 ` Oleg Drokin
2002-10-25 16:09 ` Nikita Danilov
2002-10-26 7:06 ` Valdis.Kletnieks
2002-10-30 2:32 ` Tom Vier
2002-10-30 6:36 ` Oleg Drokin
2002-10-30 7:14 ` Tom Vier
2002-10-25 21:13 ` Brett Russ
2002-10-28 10:01 ` Nikita Danilov
2002-10-26 1:41 ` Hans Reiser [this message]
2002-10-26 7:09 ` Valdis.Kletnieks
2002-10-26 13:53 ` Hans Reiser
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=3DB9F2B6.6000701@namesys.com \
--to=reiser@namesys.com \
--cc=Nikita@Namesys.COM \
--cc=icycle@charter.net \
--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.