Bugzilla – Bug 114520
crypto partition is not created during installation
Last modified: 2006-03-14 10:31:35 UTC
I wanted /local to be a crypto partition and entered the password during installation, but it is still a normal partition.
there is already an attachment #48360 [details] with y2logs.tgz at bug #114483: https://bugzilla.novell.com/attachment.cgi?id=48360
Handling of combination of partition creation and encryption was buggy. Will be fixed in RC2.
Already fixed in RC1
The bug was not fixed in 10.0 final (re-open)! - I wanted /home to be encrypted with ext3. Yast did ask for a password, but the system came up with a normal filesystem in /etc/fstab. - When trying to fix the problem with Yast, there was an unspecific error when trying to check "encrypted filesystem" without checking "format partition" for a mounted partition. - When pressing "abort" in the confirmation dialog for a partition that is to be crypto-formatted, formatting is being done! - When formatting an existing cryptoFS with a different filesystem, no crypto password is asked for (it turned out the old password had been used, which means in turn that it must have been remembered even after exiting the partitioner!).
SL 10.0 is not a version we fix such bugs any more.