https://bugzilla.novell.com/show_bug.cgi?id=332095#c7 Dirk Stoecker <opensuse@dstoecker.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #7 from Dirk Stoecker <opensuse@dstoecker.de> 2007-10-09 05:42:57 MST --- Your second paragraph contradicts your release announcements. http://www.novell.com/linux/releasenotes/i386/openSUSE/10.3/RELEASE-NOTES.en... Search for: "It is still possible to use cryptoloop via losetup and mount." Regarding dm-crypt: This means you effectively want to kill the possibility to use already crypted user-file-containers, crypted external hard-disks, crypted backup-hard-disks and crypted disk-images (CD's), which very well worked on openSUSE before 10.3 and is heavy used throughout our company, as it is the only acceptable solution to keep the company secrets save in all the locations (home disks, external disks, backup spaces, ...)? You don't mean this. This is the third time SUSE changes the encryption setup, which means I now have 3 legacy setups (twofish, twofishSL92, twofish256) and now the LUKS stuff will come. The minimum I expect is that the legacy stuff works (and it seems your release note writers thought the same way). We have about 60 crypted backup DVS's, which cannot be reencrypted and about 20 crypted partitions only in the small development department of our company. Changing this is lots of work and only to see it changed again in SUSE 11.0, as there will be another oh-so-good new solution. The setups we use are no specific options, but main options of previous SUSE releases. We expect, that they still work. In 5 to 10 years you may be right, not now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.