![](https://seccdn.libravatar.org/avatar/f9fb86af86ef66b34b610f49ebc61f39.jpg?s=120&d=mm&r=g)
Carlos E. R. wrote:
The Friday 2007-04-20 at 15:14 +0200, Ludwig Nussel wrote:
What do you need the xfs image for? You can just burn the result of encrypting zisofs.iso.
I don't know how to encrypt an iso image.
The encryption procedure I know is:
dd if=/dev/zero of=crypta.file bs=1M count=4482 losetup -T -e twofish256 /dev/loop1 crypta.file mkfs -L "EncriptedBackup" -t xfs /dev/loop1 mount -t xfs /dev/loop1 /mnt/tmp
I don't know how i can adapt mkisofs so that it creates an encrypted image.
# mkisofs -J -r -o img.iso stuff # cp img.iso img.iso.crypted # losetup /dev/loop0 img.iso.crypted # cryptsetup-twofish256 foo /dev/loop0 # cp img.iso /dev/mapper/foo # dmsetup remove foo # losetup -d /dev/loop0
Anyways. Looks like xfs doesn't work with the sector size of a cdrom. It works if you attach a loop device first and then use the loop device for cryptsetup-twofishSL92. e.g. losetup /dev/loop0 /dev/hdc cryptsetup-twofishSL92 foo /dev/loop0
You mean that the devmapping thing will not work? Because I can mount them ok without that (execept the SL92 compatibility problem, that is).
Ah, I see!
nimrodel:~ # losetup /dev/loop2 /dev/hdc nimrodel:~ # cryptsetup-twofishSL92 foo /dev/loop2 Enter passphrase: nimrodel:~ # mount /dev/mapper/foo foodir/ nimrodel:~ # l foodir/ total 4305612 ...
It works! Wow, thanks!
Good to hear. Thanks for testing! cu Ludwig -- (o_ Ludwig Nussel //\ SUSE Labs V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-security+help@opensuse.org