| [12] | 1 | $Id: TODO 250 2011-05-05 04:00:24Z tim $
|
|---|
| 2 |
|
|---|
| 3 | If you are interested in contributing to this project, here's a few
|
|---|
| 4 | things you could look into:
|
|---|
| 5 |
|
|---|
| [122] | 6 | - Currently there is no way on the command line to search for exotic
|
|---|
| 7 | paths/types. For instance, if reglookup encounters an unknown VK
|
|---|
| 8 | type, it just prints it out in Hex. However, if you wanted to search
|
|---|
| 9 | specifically for that type, there is no way to do it. Similarly, it
|
|---|
| 10 | isn't possible to specify certain binary or weird characters in
|
|---|
| 11 | paths. Reglookup should take the user path and unquote each path
|
|---|
| 12 | component using the \xQQ syntax prior to searching.
|
|---|
| 13 |
|
|---|
| [153] | 14 | - It might be nice to have a way to filter results by security
|
|---|
| 15 | descriptor information. Maybe by MTIME as well.
|
|---|
| 16 |
|
|---|
| [157] | 17 | - Testing, testing, and more testing. reglookup needs to be more
|
|---|
| 18 | heavily tested on all recent Windows platforms. A regression test
|
|---|
| 19 | suite would be nice too. Some thoughts on this include a script
|
|---|
| 20 | which randomly fuzzes an existing registry file, and tries to detect
|
|---|
| 21 | crashes of reglookup when parsing it. Another test script might
|
|---|
| 22 | randomly truncate an existing registry file, which will help improve
|
|---|
| 23 | reglookup's parsing on fragmentary files.
|
|---|
| [12] | 24 |
|
|---|
| [86] | 25 | - Unicode support still needs improvement. While parsing strings seems
|
|---|
| [163] | 26 | to be decent, UTF-8 output would be nice.
|
|---|
| [12] | 27 |
|
|---|
| [153] | 28 | - Develop and solidify regfi API. Regfi should be better documented and
|
|---|
| [163] | 29 | eventually needs a set of higher-language wrappers, starting with Python
|
|---|
| 30 | and possibly moving on to Perl as well.
|
|---|
| [86] | 31 |
|
|---|
| [163] | 32 | - Documentation. The security descriptor output format needs to be
|
|---|
| 33 | documented. Also, function contracts should be added to the
|
|---|
| [86] | 34 | lower-level functions of regfi.c.
|
|---|
| 35 |
|
|---|
| [157] | 36 | - Consider switching from libiconv to Joachim Metz's libuna for
|
|---|
| 37 | increased portability and easier builds.
|
|---|
| [86] | 38 |
|
|---|
| [12] | 39 | - Grep through the source for 'XXX', and you'll find more.
|
|---|
| [232] | 40 |
|
|---|
| 41 |
|
|---|
| 42 |
|
|---|
| 43 | 1.0 RELEASE
|
|---|
| 44 | ===========
|
|---|
| 45 |
|
|---|
| 46 | Add fields/methods for accessing security descriptors in pyregfi
|
|---|
| 47 |
|
|---|
| 48 | convert MTIME structure to uint64_t if possible
|
|---|
| 49 |
|
|---|
| 50 | investigate why file descriptors can't be directly used in Windows
|
|---|
| 51 |
|
|---|
| 52 | Fill in and update remaining regfi/pyregfi API documentation
|
|---|
| 53 |
|
|---|
| 54 | Possible debian package build rules
|
|---|
| 55 |
|
|---|
| [236] | 56 | Possibly replace reglookup-timeline with something cross-platform
|
|---|
| 57 |
|
|---|
| [232] | 58 | Testing
|
|---|
| 59 | Full diffs
|
|---|
| 60 | regfi and pyregfi threading
|
|---|
| 61 | valgrind in multiple scenarios for reglookup, reglookup-recover
|
|---|
| 62 |
|
|---|
