From: Jari Ruusu <jari.ruusu@pp.inet.fi>
To: mailerror@hushmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: loop under 2.2.20 - relative block support?
Date: Tue, 26 Feb 2002 22:58:25 +0200 [thread overview]
Message-ID: <3C7BF6F1.303DC5D0@pp.inet.fi> (raw)
In-Reply-To: <200202251943.g1PJhh231456@mailserver4.hushmail.com>
mailerror@hushmail.com wrote:
> On Mon, 25 Feb 2002 20:41:25 +0200, Jari Ruusu <jari.ruusu@pp.inet.fi> wrote:
> >If you can move original (unmodified) loop file to same block size, same
> >kernel version, then yes. If you mounted it rw, then your "time bomb"
> >exploded on your face.
> >
>
> Okay, my files are fine then, since the files were burned on cd right after I
> created them.
>
> Is this still a problem with the 2.4 loop device? In your patch for 2.4.16
> I noticed that the IV calculation is independent from the underlying block
> size. That alone would be enough to make me switch over from 2.2 ;-)
Recent versions of cryptoapi do 512 byte IV as do all versions of loop-AES
(maintained by me, http://loop-aes.sourceforge.net/). If you want to keep
using 2.2 kernels or want to use distro vendor kernels, loop-AES is better
choice as it works with all kernels and has more up to date loop fixes than
cryptoapi.
Regards,
Jari Ruusu <jari.ruusu@pp.inet.fi>
next prev parent reply other threads:[~2002-02-26 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 19:43 Re: loop under 2.2.20 - relative block support? mailerror
2002-02-26 20:58 ` Jari Ruusu [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-25 16:08 mailerror
2002-02-25 18:41 ` Jari Ruusu
2002-02-23 1:32 mailerror
2002-02-23 19:47 ` Jari Ruusu
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=3C7BF6F1.303DC5D0@pp.inet.fi \
--to=jari.ruusu@pp.inet.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=mailerror@hushmail.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.