Fedora Test Day - Encrypted Block Device Installation
WHAT
It's time to kick the tires on encrypted block device installation support in F10-Alpha. There have been several changes on this front recently, most notably the arrival of plymouth. The plan is meet and try to poke holes in encrypted block device installations. We'll have a host of QA and Development characters hanging out discussing bugs (aka "features"), expectations, and test areas. I've included details below for how you can contribute below.
WHEN
DATE: Thursday, August 14th, 2008
TIME: Between 12:00 and 21:00 UTC (8am -> 5pm EDT)
WHERE
Discussion will be held on IRC in the #fedora-qa channel. There are quite a few different IRC clients out there you can use to join the discussion, including:
- Web-based mibbit (no additional software required)- join #fedora-qa
- Chatzilla firefox extension - install Chatzilla
- A slew of popular linux clients - http://www.ircreviews.org/clients/platforms-unix.html
WHY
Have you tried installing using an encrypted block device yet? Support for installing to encrypted block devices was added in Fedora 9 (see https://fedoraproject.org/wiki/Anaconda/Features/EncryptedBlockDevices). While this support has been present for an entire release, it hasn't yet been given a thorough test review. Additionally, with the presence of plymouth, the method by which unlocking your encrypted devices has changed dramatically.
It's the new hotness and it could use your help in identifying use cases and recovery
WHO
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- dlehman
- jlaska
- bo09
- atodorov
- rwilliam
- mganisin
If you'd like to sign up to help field questions, please add your name to the list above.
HOW
There are many ways you can help, depending on your interests and skill level.
Triage Bugs
Add details on how to find eligible bugs and how to triage bugs.
Verify Fixes
Do we need details, perhaps just a small list
1. Visit a list of bugs here 1. Update 1. Select a bug to verify 1. Each bug should outline steps to reproduce
1. If you have followed those steps, and are unable to reproduce the failure, move to CLOSED RAWHIDEExploratory Testing
Add details on what this is ... and how one can go about it.
Targeted Testing
Links to the existing test matrix w/ test cases.