Carlos E. R. wrote:
Note that this is experimental. I'd try it with read only dvd images first. No warranty that it works without breaking stuff. I'd be glad if someone could confirm that the method works without corrupting filesystems indeed though (also for pre-9.2 images). Hopefully we can get rid of loop_fish2 then.
Ok, but I suppose you mean read only for the crypto filesystem, not the system itself? My system is not encrypted, would that be endangered if I was testing to read encrypted dvds?
Unlikely. The patch for dm-crypt is small and only affects loop_fish2 compatibility. The comment about sector size dependency on the dm-crypt page made me a bit cautious. Meanwhile I talked to the author and we're confident that it's not an issue. You obviously cannot corrupt a filesystem on DVD as DVD's are usually inherently read only :-)
At the moment, I have changed my crypto filesystems on the hard disk to the new system. It is only the DVDs that remain using the old loop_fish2, of course. If you think my normal filesystem would be safe (it is not encrypted), then I'm game.
Not encrypted partitions are safe.
Am I too paranoic? ;-)
Maybe, but then welcome to the club ;-) You can never be too paranoid about this stuff. Esp the fine difference between loop_fish2's twofish 256 and cryptoapi's twofish 256 can severely damage the file system if you mount or fsck it with the wrong module. You're playing with fire if you use both loop_fish2 and cryptoapi's twofish256 in parallel. 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