loop aes128 truecrypt compatible

[y23y23]

4 questions someone may be able to help with... (for the benefit of all)

MOUNT

under knoppix 6, cannot mount encrypted volume that was created with knoppix 3.7/knoppix 5
TEST CONTAINER http://jump.fm/AMUKN (Save file to your PC: click here)
password is kkkkkkkkkkkkkkkkkkkkk (20 times "k")
mount /dev/sda5 /mountpoint -o encryption=aes,keybits=128,nohashpass=1

CREATE
losetup -e aes -k 128 -N /dev/loop6 /dev/sda5
produces Knoppix 3.7 Knoppix 5 incompatible containers

FREE LOOP (knoppix 6)
mount: could not find any free loop device
how can I get more loop devices? mknod?

TRUECRYPT (windows, linux)
does anyone know if one can create/mount containers/partitions
with truecrypt that are compatible to AES128 container above?

[kl522]

FREE LOOP (knoppix 6)
mount: could not find any free loop device
how can I get more loop devices? mknod?


Not sure about the rest but this item, has been discussed before.

It's because newer version of 'mount' treat the existence of /dev/loop/0
as you intent to use the older device names, but the system only
created one, and therefore it runs out too quickly.

The fix is to remove /dev/loop/0, so that the new version of 'mount'
will use the "newer" device filenames /dev/loopX, which the system
has created with many, so it will not run out so soon.

[dinosoep]

The fix is to remove /dev/loop/0, so that the new version of 'mount'
will use the "newer" device filenames /dev/loopX, which the system
has created with many, so it will not run out so soon.

kl522, if I delete /dev/loop/0 , it just gets re-made at the next boot...

[Forester]

if I delete /dev/loop/0 , it just gets re-made at the next boot...

Yes. I would expect that. Where did you delete /dev/loop/0 ? I think you need to delete it in minirt.gz.

I find this does not work:


sudo mount -o loop /media/sdb2/KNOPPIX/knoppix-data.img yesterdaybut this does:


sudo mount -o loop=/dev/loop2 /dev/sdb2/KNOPPIX/knoppix-data.img yesterdayThere's a choice from /dev/loop0 through /dev/loop7. The first is usually taken by today's knoppix-data.img but if you're running with squashfs, then you'll find the first two are already taken.

Tchao

[kl522]

kl522, if I delete /dev/loop/0 , it just gets re-made at the next boot...

A classic example of one of those bugs which was never attended too. Yes, it is a bug in my view and I don't have to be diplomatic about it. Nevertheless you can always use the syntax which Forester proposes.

[kl522]

Can also delete the /dev/loop/0 in /etc/init.d/knoppix-autoconfig or /etc/rc.local because deleting in from minirt.gz may not be everybody's cup of tea.

[dinosoep]

knoppix@Microknoppix:/etc$ cat rc.local
#!/bin/bash
#
# rc.local
#
# Start local services after hardware detection

SERVICES="cups"

for i in $SERVICES; do
[ -x /etc/init.d/"$i" ] && /etc/init.d/"$i" start >/dev/null 2>&1
done

#for some dark reason /dev/loop/0 gets created but we want to use /dev/loop0
#so lets delete it :D
rm -r -f /dev/loop
exit 0


but still it doesn't go away...
Could it be that it doesn't look at the /unionfs/etc/rc.local but at /KNOPPIX/etc/rc.local?
cause then I would need to do a remaster...

and forester, your solution works perfect and I'm using it now. But as I'm lazy and I work a lot with loopback files I'd really need to be able to type mount -o loop ... ... .
I'll restore all the problems I've caused in the past on my system and then remaster again and let you know how it turned out :D

[kl522]

Take a look at /etc/init.d/knoppix-autoconfig, because that's the master run script for knoppix. 'knoppix-autoconfig' is defined in /etc/inittab to be executed at boot.

Somewhere in knoppix-autoconfig, it will run /etc/rc.local, but it checks if it is executable, [ -x /etc/rc.local ], before it runs it.

So please check your /etc/rc.local has execution permission.

Actually for me, I wouldn't bother with /etc/rc.local. I put my own customization into /etc/init.d/knoppix-autoconfig directly. It's bad habit of mine, perhaps I am not a good example to follow. :)

Cheers.

p/s: your rc.local seems to be doing too many things. Some of which already done in /etc/init.d/knoppix-autoconfig.

[Forester]

Can also delete the /dev/loop/0 in /etc/init.d/knoppix-autoconfig or /etc/rc.local because deleting in from minirt.gz may not be everybody's cup of tea.

Yep. Good call.

These solutions get stored in knoppix-data.img. You could also create /mnt-system/KNOPPIX/knoppix.sh for a solution that doesn't and doesn't involve grubbing around in minirt.gz.


but still it doesn't go away...

Oh dear. I can't see anything wrong with /etc/rc.local.

You try adding, instead of removing :):


for ii in $(seq 1 7); do sudo ln -s /dev/loop$ii /dev/loop/$ii; done

[dinosoep]

after a quick remaster I noticed that it now works :) there is no /dev/loop/0 anymore and I can mount just by typing moun -o loop ... ...
Could it be that knoppix really doesn't look at knoppix-data.img at the startup? or is it just coincedince it is working now?

@ kl522
that rc.local has not been messed with before by me so I'm guessing it's the one comming standard on the cd... Does that mean that rc.local on the cd is not the way it's suposed to be?

[Forester]

but still it doesn't go away...
Could it be that it doesn't look at the /unionfs/etc/rc.local but at /KNOPPIX/etc/rc.local?
cause then I would need to do a remaster...


I got rid of it with:


sudo rm -fr /lib/udev/devices/loopand a reboot. No remaster necessary.

Somewhere in knoppix-autoconfig it copies a load of devices from /lib/udev/devices to /dev but it does that long before it runs rc.local. Perhaps your rc.local wasn't executable.