Hi! > > I'd like to retain ability to read suspend image in any order (so that > > code can be reused for swap encryption, etc). > > This is not possible with cipher block chaining as used right now. One > would have to use a non-random iv set needs to set for every page. And > this leads to exactly the same problem why dm-crypt now offers the > 'essiv' mode. I don't know if a random access feature is worth this > effort as sequential disk access (sequential write, sequential read) is > usally the fastest method anyway.
I thought I'd just reuse your code for automagic swap encryption. Oh well. > For regular swap encryption I do hope that the initrd feature of swsup2 > will eventually find its way into the mainline kernel. This way you can > have an external key for dm-crypt to access the encrypted swap > partition. Check -mm kernel, swsusp1 can now do resume from initrd. Pavel -- Boycott Kodak -- for their patent abuse against Java. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/