Summary: | sys-apps/util-linux-2.13 - cryptoloop gone | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tilman Giese <gentoo> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Tilman Giese
2007-09-03 20:42:55 UTC
*** This bug has been marked as a duplicate of bug 190819 *** Just a question for clarification: Is this really a duplicate of bug 190819? I am talking about the cryptoloop approach and the decryption itself that is not working whereas bug 190819 is talking about the dm-crypt approach and a name mismatch of the devices. To my mind, these are two separate things. (In reply to comment #2) > am talking about the cryptoloop approach In that case - INVALID. That patch is gone, dead, removed. As far as I know, cryptoloop is only deprecated but not removed from util-linux. And indeed, I am able to mount file systems encrypted with 'twofish' using cryptoloop, but I am not able to use 'twofish256' as encryption algorithm. I've the same problem! Please fix. SAME PROBLEM, someone PLEASE FIX! Got the same problem after upgrading to util-linux-2.13. Temporary workaround: downgrade to util-linux-2-12-r1, so you can at least access your files :) |