[Pkg-cryptsetup-devel] TODO list

[gebi at sbox.tugraz.at]

Quoting Jonas Meurer <jonas at freesources.org>:

> * provide support for LVM on encryped devices
>   - check for existance of source device before running cryptsetup

Is it really necessary in the long term?
What if we just implement better errorhandling in cryptsetup?

> * improve the checks
>   - distinguish between luks, plain cryptsetup and swap
>    swap:
>      + precheck for any existing filesystem, fail if possitive

really?
if the partition has type swap, why should we care?
every live-cd out there whipes a partition with mkswap if it is of  
type swap (id 82).

>      + postcheck for nothing, just go ahead with mkswap, swapon

ok

and no the ugly one :(
>    plain cryptsetup:
>      + precheck for any existing filesystem, fail if possitive

couldn't be avoided :(.

>      + postcheck for the expected filesystem, fail if negative

couldn't be avoided also :(, or any other ideas?
But why should we check if a mount does allready fail?
print a warning for possible false pw or false partition?

>    luks cryptsetup:
>      + precheck for a valid luks partition, fail if negative

yes.

>      + postcheck for the expected filesystem, fail if negative

why?
if luksOpen succeeds it is the right data. Why sould we check if there  
is a filesystem? Who says that there should be a filesystem on the  
cryptovolume?

> feel free to add your ideas ;)

*hehe* ;)

greets,
Michael