Page MenuHomeLubuntu

Swap might be used by default in partitioning but errors out because it's a security vulnerability
Closed, ResolvedPublic


I just remember this happening but QA should scope this out while we're working on QA improvements for UEFI and LVM installs.

I don't remember if it was with Encrypted LVM or just LVM (or maybe just the default install) but I remember installing Lubuntu at one point and it (rightfully) errored out on me because the swap was unencrypted and it's a security vuln for it to be done that way.

Could someone from QA scope this out to see if it's reproducible, and if it is, figure out a potential solution?


Event Timeline

tsimonq2 created this task.Nov 26 2017, 1:16 PM
tsimonq2 created this object in space S1 Public.
tsimonq2 created this object with visibility "Public (No Login Required)".
tsimonq2 created this object with edit policy "QA (Project)".
tsimonq2 updated the task description. (Show Details)
wxl added a comment.Nov 27 2017, 1:03 AM

kind of depends on T4: Fix the missing UEFI packages to actually check widely.

wxl moved this task from New to Blocked on the QA board.Nov 27 2017, 8:38 AM
tsimonq2 moved this task from Blocked to New on the QA board.Nov 27 2017, 8:03 PM

Not really @wxl, I figured out how to reproduce it. When installing Lubuntu using the latest Daily Live image with virt-manager and UEFI emulation, when selecting LVM and encryption for the disk setup, it barfs this at me:

(click for a bigger image)

This doesn't seem to be because of the installer but the configuration that it tries to install. It's probably a global issue too, given the nature of the problem

Could you please talk with someone about this @wxl to see if we can get it sorted? (Maybe file a bug somewhere?)

wxl added a comment.Nov 28 2017, 11:46 AM

Did a little bug searching and there are many - similar bugs. There's even one that seems possibly related, but affects Qt ubiquity. This is ooooold. The swapoff suggestion is certainly a reasonable one and one that's been a workaround in the past. That said, I've pinged cyphermox in hopes that he can provide some help.

Then I guess it's a good thing we're fixing old-but-still-relevant bugs, eh @wxl? 😛

tsimonq2 raised the priority of this task from High to Unbreak Now!.Dec 8 2017, 8:24 AM
tsimonq2 moved this task from New to Blocked on the QA board.

Bump on this?

Bump. This needs to be fixed as soon as possible.

tsimonq2 closed this task as Resolved.May 16 2018, 2:25 PM

This was fixed last cycle.