## Note: this is my personal todo and ideas list (alexh@)
-* dm pdev bounds checking
-<pre>
-19:38:08 dragon:~
-# dmsetup deps
-foocrypt: 1 dependencies : (0, 0)
-foocrypt2: 1 dependencies : (0, 0)
-foocrypt3: 1 dependencies : (0, 0)
-19:38:09 dragon:~
-# dmsetup table
-foocrypt: 0 1021944 crypt aes-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 /dev/ad0s0a 2056
-foocrypt2: 0 1021944 crypt aes-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 /dev/ad0s0a 2056
-foocrypt3: 0 1021944 crypt aes-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 /dev/ad0s0a 2056
-</pre>
-
* Commit hook reminding people of MFCs to stable
- also broadcast about http://gitweb.dragonflybsd.org/dragonfly.git/blob/HEAD:/tools/gittemplate
* add a communication channel mechanism to dm
- essentially a way to send messages and receive responses to dm target instances
-* dm_target_crypt
- - Look at plain64 iv support, what it implies vs plain.
- - Think about benbi iv support
-
* Add TrueCrypt support
- Simply add a userland tool that sets dm_target_crypt up with the right parameters, extracted from the TrueCrypt header
- https://github.com/bwalex/tc-play <- done!