Bug 475399

Summary: livecd-tools: use ext2, fill crypt target with /dev/urandom first, handle password typos
Product: [Fedora] Fedora Reporter: Matt Domsch <matt_domsch>
Component: livecd-toolsAssignee: Jeremy Katz <katzj>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: davidz, katzj
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-12-19 18:57:10 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:
Attachments:
Description Flags
livecd.patch none

Description Matt Domsch 2008-12-09 03:05:08 UTC 
Created attachment 326256 [details]
livecd.patch

Description of problem:
1) ext2 should be nicer than ext3 for flash.  There's no good reason to journal with the flash, and it just chews up write cycles.

2) if you're going to use an encrypted volume, it's best to pre-fill the volume with random data.  Using /dev/urandom, it's fast enough.  Only do this for non-sparse-file-backed encrypted home.  Could arguably drop sparse-file-backed encrypted home and do this everywhere, but that would definitely be slower.

3) if any of the cryptsetup commands fail (bad password typed), keep trying.  Otherwise, a typo means the whole process dies badly and you have to start from scratch.

Version-Release number of selected component (if applicable):
git head
Comment 1 Jeremy Katz 2008-12-19 18:57:10 UTC 
Not journaling increased the chances of ending up with a corrupted /home in cases of, eg, just turning the computer off.

Went ahead and pushed the other bits, though