> Ok... it works. All of them. It was my fault. Between two of the > tests I forgot I had replaced the encrypted dvd with the 10.3 dvd.
:-) >> I use encrypted CDs and DVDs too, usually I generate a random file >> and loop-mount it, & save an accompanying md5 to check if it >> refuses a mount. Usually it's because it's scratched or dirty, or I >> have the wrong password. > > I don't follow this part :-? Getting a bit OT but: I create a regular file of rubbish, and loop-mount it with crypto before generating a filesystem and finally mounting normally: $ dd if=/dev/urandom of=file.img count=700 bs=1048576 (i.e. owner=user) # losetup -e twofish256 /dev/loop0 file.img # mkfs.ext3 /dev/loop0 # mount -t ext3 -o rw /dev/loop0 mountpoint Copy what I want to keep to mountpoint then: # umount mountpoint # losetup -d /dev/loop0 $ md5sum file.img > file.md5 (i.e. owner=user again) Then write file.img and file.md5 to cd using k3b. Easy to test integrity without having to crypto-mount: $ cd cd-mountpoint $ md5sum -c file.md5 And to mount for reading # losetup -e twofish256 /dev/loop0 cd-mountpoint/file.img # mount -t ext3 -o ro /dev/loop0 mountpoint Not too hard to script these steps, except for the problem with cd mount-point names under /media. Of course, same idea for DVDs. I generally use this scheme for backups of documents, emails etc. - not spectacularly secret, but potentially useful to an ID thief. Most ordinary punters won't be able to read it, but of course GCHQ / NSA etc. wouldn't take very long if they ever wanted to... A lot of people take essentially no backups, and many of those who do take them leave unprotected data lying around. Not very sensible really! -- Regards, Richard (MQ) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
