oem-config process that zero's swap broken on armel preinstalled images

This probably needs an additional check in user-setup-apply to only use an unlimited copy from /dev/zero when swap is a block device, and limit it to the current size when swap is a file.

the problematic code in user-setup-apply is:

        if [ -n "$ENCRYPT_HOME_OPT" ] && [ -e $ROOT/etc/crypttab ]; then
                # Zero out all encrypted swap partitions. It is assumed that
                # passwords are not used beyond this point in the install.
                # cryptswap0 /dev/sda5 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
                # Ideally we would set up a new progress bar here, but we're
                # inside finish-install's and cdebconf doesn't support nested
                # progress bars.
                db_progress INFO user-setup/progress/wipe-swap
                while read name device source options; do
                        if echo "$options" | grep -q "swap"; then
                                if swapoff $device; then
                                        dd if=/dev/zero of=$device 2>/dev/null || true
                                fi
                        fi
                done < $ROOT/etc/crypttab
        fi

some testing for blockdevices and files (if [ -b $device ] ...) needs to be added here.
in case a file is detected, the size needs to be handed over to dd.

Release Note:

"On the current preinstalled images for Ubuntu ARM a bug (number 646421) exists that will grow the swap file to occupy the full free space of your SD card if you select to use an encrypted home dir during install. There is currently no workaround but to not select this option, a fix for this bug is in progress."

This bug was fixed in the package user-setup - 1.28ubuntu9

---------------
user-setup (1.28ubuntu9) maverick; urgency=low

  * make zeroing swap work also with swapfiles if encrypted home
    is selected (LP: #646421)
 -- Oliver Grawert <email address hidden> Sat, 02 Oct 2010 01:23:03 +0200

Also note that this "dd" should specify a blocksize, rather than defaulting to 512 byte writes. This will vastly speed up the process of clearing encrypted swapspace. See bug #432422.

Should this issue be removed from the release notes?