Description of problem:
Manually setting up encrypted swap post-install using "/dev/urandom" as the key,
and "swap" as an option in /etc/crypttab to reformat it works fine (supported by
/etc/rc.sysinit) until a kernel update comes along and does its mkinitrd, which
then overrides this by using the first swap in /etc/fstab as an encrypted
swsuspdev resume device. You're then prompted to manually enter the luks
password, which doesn't exist in this case, because encrypted swap is being
recreated with a random key on each boot.

Version-Release number of selected component (if applicable):
mkinitrd-6.0.52-2.fc9.x86_64

How reproducible:
After installing a kernel update

Steps to Reproduce:
1. Do a default F9 install (without any disk encryption)
2. Convert LogVol01 swap to luksFormat encrypted swap using /dev/urandom as key:
 a. swapoff /dev/mapper/VolGroup00-LogVol01
 b. cryptsetup -d /dev/urandom create luks-VolGroup00-LogVol01
/dev/mapper/VolGroup00-LogVol01
 c. mkswap /dev/mapper/luks-VolGroup00-LogVol01
 d. swapon /dev/mapper/luks-VolGroup00-LogVol01
 e. echo "luks-VolGroup00-LogVol01  /dev/mapper/VolGroup00-LogVol01 
/dev/urandom  swap" >> /etc/crypttab
 f. modify /etc/fstab to use "/dev/mapper/luks-VolGroup00-LogVol01" as the new
encrypted swap device (which needs to be the first swap in fstab for mkinitrd to
use it)
3. Reboot and "swapon -s" to verify that encrypted swap was automatically setup
using /dev/urandom as key per /etc/crypttab.
4. Update the kernel, or manually run mkinitrd: mkinitrd -v -f
/boot/initrd-$(uname -r).img $(uname -r)
5. Reboot once more
  
Actual results:
the newly generated initrd is now doing its own early cryptsetup for swap and
prompting for a non-existent luks password.

Expected results:
mkinitrd should parse /etc/crypttab and exclude doing cryptsetup for swap if the
user is using /dev/urandom, /dev/random, or /dev/hw_random as a reinitialization
key.  (akaik, /dev/urandom can't exist in initrd so excluding it is the best option)

Additional info:
there might be similar issues if using a keyfile VS /dev/urandom

As a temporary workaround I've just hacked /sbin/mkinitrd to exclude my specific
swap device:

emitcrypto()
{
    # parse /etc/crypttab instead at some point and exclude any entry
    # where field #3 is /dev/urandom and #4 is "swap"
    # also: add "export noresume=1" to /etc/sysconfig/mkinitrd
    if [ "$2" != "luks-vgr10-swapcrypt" ]; then
        emit "echo Setting up disk encryption: $1"
        emit "cryptsetup luksOpen $1 $2"
    fi
}