This all could be entirely my fault, of course, but I always just did it "the default" way.
Here is the table with the old ("correct") cipher:
pvsvie0401_1-cbackup_1: 0 3907018752 linear 8:17 384
backup_1: 0 3907018752 crypt aes-cbc-plain
0000000000000000000000000000000000000000000000000000000000000000 0 254:1 0
pvsvie0401_0-cbackup_0: 0 580206592 linear 8:3 39059840
backup_0: 0 580206592 crypt aes-cbc-plain
0000000000000000000000000000000000000000000000000000000000000000 0 254:2 0
and with the new ("broken") cipher:
pvsvie0401_1-cbackup_1: 0 3907018752 linear 8:17 384
backup_1: 0 3907018752 crypt aes-cbc-essiv:sha256
0000000000000000000000000000000000000000000000000000000000000000 0 254:1 0
pvsvie0401_0-cbackup_0: 0 580206592 linear 8:3 39059840
backup_0: 0 580206592 crypt aes-cbc-essiv:sha256
0000000000000000000000000000000000000000000000000000000000000000 0 254:2 0
hop
--
What should you do to a blue elephant? Cheer it up.
smime.p7s
Description: S/MIME cryptographic signature
