Bug 88224
Summary: | Awkward reaction to loopback encrypted filesystems | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Mark Stoneburner <markdoe7> |
Component: | installer | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | Keywords: | FutureFeature |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-21 20:37:47 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mark Stoneburner
2003-04-07 20:10:41 UTC
We don't currently support using the crypto loop stuff in the userspace tools, so this is a little tricky to handle. I'll try to add something to do a little better, but the current case might be the best that's possible until we integrate crypto loop support for the distro. Cryptoloop has been replaced with dm-crypt. This bug is very old. Is this still relevant? Does anaconda complain about dm-crypt filesystems? This isn't really relevant anymore now that cryptoloop is obsoleted. We don't really handle dm-crypt, but the reaction should be better |