From: Jari Ruusu <jari.ruusu@pp.inet.fi>
To: spam goes to /dev/null <spam-goes-to-dev-null@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: serpent loopback crypto "EXT2-fs: group descriptors corrupted"
Date: Sun, 20 May 2001 23:11:13 +0300 [thread overview]
Message-ID: <3B0824E1.4FEE834F@pp.inet.fi> (raw)
In-Reply-To: <01df01c0e0a6$bfb9ed40$0100005a@host1>
spam goes to /dev/null wrote:
> i created a 10mb file called .enc2 with random data and ran "# losetup -e
> serpent -k 128 /dev/loop0 /mnt/hda7/.enc2"
> then i ran "# mke2fs /dev/loop0" and tried to "# mount /dev/loop0 /enc". but
> i get the following error messages when trying to mount:
>
> May 19 21:32:10 HOST2 kernel: EXT2-fs error (device loop(7,0)):
> ext2_check_descriptors: Block bitmap for group 16 not in group (block 0)!
> May 19 21:32:10 HOST2 kernel: EXT2-fs: group descriptors corrupted !
>
> im using kernel 2.4.4 patched with crypto patch 2.4.3.1 [and util linux
> 2.11a patched with the patch from that crypto patch]
> i also got the same errors with a 2gb file and by creating the loop device
> directly on my 19.5gb /dev/hda7
> i tried a few times again and sometimes the encrypted loopback fs works
> perfectly, sometimes the error occurs!?
> anyone got an idea what this is!? i will supply more information on request
International crypto patch is misdesigned and broken, period. If you don't
want to play russian roulette with your data, you should consider using
loop-AES package. loop-AES announcement is here:
http://mail.nl.linux.org/linux-crypto/2001-05/msg00003.html
Regards,
Jari Ruusu <jari.ruusu@pp.inet.fi>
prev parent reply other threads:[~2001-05-20 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-19 21:00 serpent loopback crypto "EXT2-fs: group descriptors corrupted" spam goes to /dev/null
2001-05-20 20:11 ` Jari Ruusu [this message]
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=3B0824E1.4FEE834F@pp.inet.fi \
--to=jari.ruusu@pp.inet.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=spam-goes-to-dev-null@gmx.net \
/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.