mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: mailerror@hushmail.com
To: Jari Ruusu <jari.ruusu@pp.inet.fi>
Cc: linux-kernel@vger.kernel.org, mailerror@hushmail.com
Subject: Re: Re: loop under 2.2.20 - relative block support?
Date: Mon, 25 Feb 2002 11:43:43 -0800	[thread overview]
Message-ID: <200202251943.g1PJhh231456@mailserver4.hushmail.com> (raw)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 25 Feb 2002 20:41:25 +0200, Jari Ruusu <jari.ruusu@pp.inet.fi> wrote:
>mailerror@hushmail.com wrote:
>> On Sat, 23 Feb 2002 21:47:56 +0200, Jari Ruusu <jari.ruusu@pp.inet.fi> wrote:
>> >Kerneli patches use block size dependant IV computation (also called "time
>> >bomb" IV). Shit hits the fan when you move files to a device with different
>> >block size. Search linux-crypto archives for more information.
>>
>> Aha. So if I moved the loopback file onto a partition with the same blocksize
>> again, it would all be fine?
>
>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 ;-)

thanks a lot..
mailerror

Hush provide the worlds most secure, easy to use online applications - which solution is right for you?
HushMail Secure Email http://www.hushmail.com/
HushDrive Secure Online Storage http://www.hushmail.com/hushdrive/
Hush Business - security for your Business http://www.hush.com/
Hush Enterprise - Secure Solutions for your Enterprise http://www.hush.com/

-----BEGIN PGP SIGNATURE-----
Version: Hush 2.1
Note: This signature can be verified at https://www.hushtools.com

wl4EARECAB4FAjx6lMEXHG1haWxlcnJvckBodXNobWFpbC5jb20ACgkQb539PwJB5JNC
zQCdFCCDIQTekRvch+NwN2Z2mU4SOmIAoK5Z9j5SMGaxOLPUPnWw9N6zxR/J
=BmUy
-----END PGP SIGNATURE-----


             reply	other threads:[~2002-02-25 19:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-25 19:43 mailerror [this message]
2002-02-26 20:58 ` Jari Ruusu
  -- strict thread matches above, loose matches on Subject: below --
2002-02-25 16:08 mailerror

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=200202251943.g1PJhh231456@mailserver4.hushmail.com \
    --to=mailerror@hushmail.com \
    --cc=jari.ruusu@pp.inet.fi \
    --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®