re: In-kernel units for block numbers, etc ...

[matthew green <mrg%eterna.com.au@localhost>]

> The current code operates on full sectors and encodes the sector number
> into the data.
> 
> Modifying this to encode multiple 512 byte blocks instead and using
> block numbers instead of sector numbers looks straight forward to me.
> 
> We just have to decide if that is a good thing. Or maybe it needs to
> be configurable?

i think it should use 512 byte crypto blocks in all cases, using
offset in DEV_BSIZE units as part of the IV, at least by default.

that would at least allow data to be recovered, by default, from
the wrong sized media.


.mrg.