All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@oddball.prodigy.com>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1 cryptoloop & aes
Date: Tue, 29 Jul 2003 19:28:39 -0400	[thread overview]
Message-ID: <200307291928.39288.davidsen@oddball.prodigy.com> (raw)
In-Reply-To: <20030720103852.A11298@pclin040.win.tue.nl>

On Sunday 20 July 2003 04:38 am, Andries Brouwer wrote:
> On Sat, Jul 19, 2003 at 05:57:26PM -0700, Hielke Christian Braun wrote:
> > Then i installed the losetup from util-linux-2.12pre.
>
> You need util-linux-2.12 or later.
>
> (try ftp://ftp.cwi.nl/pub/aeb/util-linux or so)
>
> Andries

Thank you, that's the missing part. I will say that in limited use I have used 
aes and twofish and they seem to work correctly. I copied a bunch of data 
there, checked it against the md5 contents file and all data was correct, did 
a bunch of renames, slinks, compiles, etc. unmounted and remounted a few 
times. So far so good, this isn't critical data, but I'm leaning that way for 
my laptop.

All this with 2.6.0-test1-ac2.

Now, for the bizarre test case, suppose I did three encrypted losetups, each 
using a different encryption. Then I made a raid-5 array of the three loop 
devices. created a filesystem on the md device, and ran on that. Forget the 
practicality, this is a test to see of the parts are robust, can I do it and 
will it work?

Now make two of those filesystems losetups of NBDs. Now I can recover if any 
one machine is missing, no one can recover the data without compromising at 
least two machines. again, forget practical, this is a test and maybe has 
application to the devout fundamentalist paranoid. If I was going to do it 
I'd loopback mount the md device, too ;-)

  parent reply	other threads:[~2003-07-29 23:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20  0:57 2.6.0-test1 cryptoloop & aes Hielke Christian Braun
2003-07-20  8:38 ` Andries Brouwer
2003-07-20 21:38   ` 2.6.0-test1 cryptoloop & aes & xfs Hielke Christian Braun
2003-07-20 22:15     ` Andries Brouwer
2003-07-21 17:12     ` Jeff Sipek
2003-07-22  0:24       ` Hielke Christian Braun
2003-07-22 11:54         ` Jari Ruusu
2003-07-29 23:28   ` Bill Davidsen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-20  8:22 2.6.0-test1 cryptoloop & aes Benjamin Weber

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=200307291928.39288.davidsen@oddball.prodigy.com \
    --to=davidsen@oddball.prodigy.com \
    --cc=aebr@win.tue.nl \
    --cc=davidsen@tmr.com \
    --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 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.