I can't encrypt a filesystem with Puppy's aes

[Mazzo]

Hi

I am trying to set up an encrypted filesystem using losetup-FULL and aes encryption. It doesn't work!

Barry used xor encryption for the pup001 on usb / hard drive, but I would prefer something a little stronger.

the command would be:

losetup-FULL -e aes /dev/loopx filename

It allows me to put in a password (although it expects 20 characters) but then fails.

I have setup succesfully a filesystem on ubuntu which works fine, but when trying to mount it in puppy, it fails. It may be the aes is different.

Anyone any ideas? Is the aes in puppy purely for wireless networking?

The command to mount would be:
mount -t umsdos -o loop filename /mountpoint -oencryption=aes

If there is another strong and reasonably quick alternative to aes that is easy to put into puppy, it would be good to know. I don't want to (and worry about my capability) of recompiling the kernel.

Here's hoping someone else has tried it (and been successful!)

[BarryK]

I wonder if the aes.o module is getting loaded.
It probably should happen automatically, but just in case, you could try "modprobe aes".

[Mazzo]

Hi Barry - thanks for replying.

It seems to be loaded - it certainly asks for a 20 character password which xor doesn't.

[Mazzo]

I still cannot get aes to work at all with losetup-Full.

I can get xor to work, but it is really weak (it looks to me that the password is visible in the file if you view it in a text editor!). Maybe I am doing something wrong?

The idea would be to create an encrypted pup00x on a usb or HD so that only you can access it.

Is there anyone who is able to help with this? I think (stands by to be corrected ) that I have done my homework and that aes encryption is both pretty secure and also quick for loopback systems.

When trying to:
losetup-FULL -e aes /dev/loopn filename

I simply get
ioctl: LOOP_SET_STATUS: Invalid argument

This doesn't happen if aes is changed to xor.