Bug 88510

Summary: losetup doesn't support -e option
Product: [Retired] Red Hat Linux Reporter: Brian G. Anderson <bikehead>
Component: mountAssignee: Bernhard Rosenkraenzer <bero>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: athlon   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:52:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Brian G. Anderson 2003-04-10 16:28:31 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
"losetup -e aes /dev/loop /var/myfile"

returns "Unsupported encryption type aes".  I've done a modprobe of
cryptoloop, cipher-aes and everything else I can think of.

Of course this will cause the mount command to fail when trying to mount an
encrypted loop filesystem.

I notice that RH8.0 had shipped with a problem where certain utilities--losetup
being one--were not crypto aware even though the stock kernel was compiled with
crypto support.  Is the same problem going on here?

Does RH have some other preferred way of doing encrypted filesystems?  I would
think this is a fairly standard feature.



Version-Release number of selected component (if applicable):
losetup-2.11y-9

How reproducible:
Always

Steps to Reproduce:
1. use dd if=/dev/urandom of=/tmp/crypt bs=1M count=100
2. modprobe cryptoloop cipher-aes
3. losetup -e aes /dev/loop0 /tmp/crypt
    

Actual Results:  Error message: Unsupported encryption type aes

Expected Results:  Should prompt me for a password to build the encrypted loop

Additional info:

There is a similar bug entered for RH8.0 which ultimately refers back to a bug
entered for RH6.2 56698.  All bugs are closed with no indication of why this
isn't fixed.

Comment 1 Nils Philippsen 2003-07-12 13:48:38 UTC

*** This bug has been marked as a duplicate of 56698 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:52:36 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.