Hi,
I'm trying to create an encrypted filesystem via Yast partitioner in SuSE
10.1, using a file mounted via the loop device. I have done this before,
in fact I have two such things created under 9.3 running; but I can't
(couldn't) with 10.1, it is creating a plain non encrypted filesystem
instead.
Or so it seemed.
Looking carefully again, after several runs, I noticed that it was
mounting the filesystem as plain non encrypted, but it was in fact
creating an encrypted one with the appropriate entry en /etc/cryptotab
instead of in /etc/fstab - whereas in 9.3 it created then in /etc/fstab
instead, and in 8.x they were created in /etc/cryptotab. This criteria
change is very confusing. Perhaps Yast could ask where the user wanted to
define it - feature request, perhaps?
It's not only a config file difference; an encrypted filesystem defined in
/etc/fstab can be mounted with the command mount, but one defined in
/etc/cryptotab is mounted via the command "/etc/init.d/boot.crypto start",
which is less comfortable for manual mount after boot (and it mounts all
devices listed, even if already mounted).
/etc/cryptotab sample line:
/dev/loop3 /file3 /crypta3 ext3 twofish256 acl,user_xattr
/etc/fstab, the equivalent sample line:
/file3 /crypta3 ext3 noauto,acl,user_xattr,loop=/dev/loop3,encryption=twofish256 0 0
Both work with the same file, I tried. I'll stay with the second one. But
in 9.3 the fstab line was instead (incompatible):
/file2 /crypta2 ext3 noauto,acl,user_xattr,loop=/dev/loop2,encryption=twofish256,phash=sha512,itercountk=100
Comments?
Also, how would I create the equivalent encrypted filesystem manually;
docus, howtos?
Tks.
--
Cheers,
Carlos Robinson