Bug 136152

Summary: losetup manpage crypt options/examples are far off reality
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Andreas Kleen <ak>
Component: BasesystemAssignee: Matthias Koenig <mkoenig>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: junk26, suse-beta
Version: RC 4   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Andreas Kleen 2005-11-30 18:11:15 UTC 
A lot of the stuff described there doesn't work, e.g. the multi key 
option and the example. The kernel code only supports single keys.
When you try to use multi keys it just fails with an error message
aboput unsupported ioctls.

To reproduce: try the example at the end of the losetup manpage

I think the example should be changed to something that actually works 
with the shipped kernel. And options that don't work either should
be hidden or at least clearly marked.

Another problem is that it tries to get a lot of entropy
and may stall for a long time. It should give hints on how
to get more entry or how to use /dev/hw_random if available
Comment 1 Hendrik Vogelsang 2006-02-01 17:58:17 UTC 
i have a look
Comment 2 Hendrik Vogelsang 2006-06-01 18:02:58 UTC 
*** Bug 180111 has been marked as a duplicate of this bug. ***
Comment 3 Matthias Koenig 2006-10-06 13:00:10 UTC 
Mostly all of this is from the loop-aes patch. As I can not see that we support this in our kernel (and it has recently been proposed to use dm-crypt with LUKS as default cryptofs), I have no idea why we should still carry it in util-linux. 
If there is no intention to support loop-aes by our kernel, I propose to drop loop-aes patch from util-linux at all.
Comment 4 Matthias Koenig 2007-04-11 12:22:56 UTC 
fixed in stable
loop-AES patch has been removed from util-linux