source: doc/TODO @ 221

Last change on this file since 221 was 221, checked in by tim, 13 years ago

added a lot of documentation for pyregfi and a few more attributes

  • Property svn:keywords set to Id
File size: 1.8 KB
Line 
1$Id: TODO 221 2011-04-02 03:42:08Z tim $
2
3If you are interested in contributing to this project, here's a few
4things you could look into:
5
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
14 - It might be nice to have a way to filter results by security
15   descriptor information.  Maybe by MTIME as well.
16
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.
24
25 - Unicode support still needs improvement.  While parsing strings seems
26   to be decent, UTF-8 output would be nice.
27
28 - Develop and solidify regfi API.  Regfi should be better documented and
29   eventually needs a set of higher-language wrappers, starting with Python
30   and possibly moving on to Perl as well.
31
32 - Documentation.  The security descriptor output format needs to be
33   documented.  Also, function contracts should be added to the
34   lower-level functions of regfi.c.
35
36 - Consider switching from libiconv to Joachim Metz's libuna for
37   increased portability and easier builds.
38
39 - Grep through the source for 'XXX', and you'll find more.
Note: See TracBrowser for help on using the repository browser.