Changeset 119
- Timestamp:
- 08/09/08 01:55:45 (16 years ago)
- Location:
- trunk/doc
- Files:
-
- 1 added
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/Makefile
r64 r119 1 1 # $Id$ 2 2 3 BUILD_FILES=$(BUILD_DOC)/man/man1/reglookup.1.gz $(BUILD_DOC)/man/man1/reglookup-timeline.1.gz 3 BUILD_FILES=$(BUILD_DOC)/man/man1/reglookup.1.gz\ 4 $(BUILD_DOC)/man/man1/reglookup-timeline.1.gz\ 5 $(BUILD_DOC)/man/man1/reglookup-recover.1.gz 4 6 5 7 default: $(BUILD_FILES) 6 8 7 $(BUILD_DOC)/man/man1 /reglookup.1.gz: man/man1/reglookup.1.gz9 $(BUILD_DOC)/man/man1: 8 10 mkdir -p $(BUILD_DOC)/man/man1 11 12 $(BUILD_DOC)/man/man1/reglookup.1.gz: man/man1/reglookup.1.gz $(BUILD_DOC)/man/man1 9 13 cp man/man1/reglookup.1.gz $@ 10 14 11 $(BUILD_DOC)/man/man1/reglookup-timeline.1.gz: man/man1/reglookup-timeline.1.gz 12 mkdir -p $(BUILD_DOC)/man/man1 15 $(BUILD_DOC)/man/man1/reglookup-timeline.1.gz: man/man1/reglookup-timeline.1.gz $(BUILD_DOC)/man/man1 13 16 cp man/man1/reglookup-timeline.1.gz $@ 17 18 $(BUILD_DOC)/man/man1/reglookup-recover.1.gz: man/man1/reglookup-recover.1.gz $(BUILD_DOC)/man/man1 19 cp man/man1/reglookup-recover.1.gz $@ 14 20 15 21 install: … … 22 28 docbook2x-man --to-stdout reglookup.1.docbook > man/man1/reglookup.1 23 29 docbook2x-man --to-stdout reglookup-timeline.1.docbook > man/man1/reglookup-timeline.1 30 docbook2x-man --to-stdout reglookup-recover.1.docbook > man/man1/reglookup-recover.1 24 31 cd man/man1 && gzip -9 -f reglookup.1 25 32 cd man/man1 && gzip -9 -f reglookup-timeline.1 33 cd man/man1 && gzip -9 -f reglookup-recover.1 -
trunk/doc/reglookup-timeline.1.docbook
r91 r119 9 9 <refnamediv id='name'> 10 10 <refname>reglookup-timeline</refname> 11 <refpurpose> windows NT+ registry MTIME timeline generator</refpurpose>11 <refpurpose>Windows NT+ registry MTIME timeline generator</refpurpose> 12 12 </refnamediv> 13 13 … … 28 28 This script is a wrapper for <command>reglookup(1)</command>, and reads 29 29 one or more registry 30 files to produce an MTIME 30 files to produce an MTIME-sorted output. This is helpful when building 31 31 timelines for forensic investigations. 32 32 </para> … … 99 99 distribution. 100 100 </para> 101 <para> 101 <para> 102 102 This program is distributed in the hope that it will be useful, 103 103 but WITHOUT ANY WARRANTY; without even the implied warranty of 104 104 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 105 GNU General Public License version 2for more details.105 GNU General Public License version 3 for more details. 106 106 </para> 107 107 </refsect1> … … 110 110 <title>SEE ALSO</title> 111 111 <para> 112 reglookup(1) 112 reglookup(1) reglookup-recover(1) 113 113 </para> 114 114 </refsect1> -
trunk/doc/reglookup.1.docbook
r87 r119 9 9 <refnamediv id='name'> 10 10 <refname>reglookup</refname> 11 <refpurpose> windows NT+ registry reader/lookup tool</refpurpose>11 <refpurpose>Windows NT+ registry reader/lookup tool</refpurpose> 12 12 </refnamediv> 13 13 … … 27 27 print them out to stdout in a CSV-like format. It has filtering 28 28 options to narrow the focus of the output. This tool is 29 designed to work with on windows NT/2K/XP/2K3 registries, though30 your mileage may vary.29 designed to work with on Windows NT/2K/XP/2K3/Vista registries, 30 though your mileage may vary. 31 31 </para> 32 32 </refsect1> … … 61 61 Specify a type filter. Only elements which match this 62 62 registry data type will be printed. Acceptable values 63 are: 63 are: 64 64 <command> 65 65 NONE, SZ, EXPAND_SZ, BINARY, DWORD, DWORD_BE, … … 111 111 information from key security descriptors. The columns 112 112 are: owner, group, sacl, dacl. 113 (This feature's output probably contains bugs right now.)113 (This feature's output has not been extensively tested.) 114 114 </para> 115 115 </listitem> … … 152 152 <para> 153 153 Required argument. Specifies the location of the 154 registry file to read. T ypically, these files willbe155 found on a NTFS partition under154 registry file to read. The system registry files should be 155 found under: 156 156 <command>%SystemRoot%/system32/config</command>. 157 157 </para> … … 293 293 <title>BUGS</title> 294 294 <para> 295 This program has only been tested on a few different systems.296 (Please report results to the development list if you test it297 on Windows NT 4.0, 2003, or Vista registries. Also, if you298 test on any 64-bit architecture, please contact us.)295 This program has been smoke-tested against most current Windows target 296 platforms, but a comprehensive test suite has not yet been developed. 297 (Please report results to the development mailing list if you encounter 298 any bugs. Sample registry files and/or patches are greatly appreciated.) 299 299 </para> 300 300 <para> … … 314 314 Backslashes are currently considered special characters, to make 315 315 parsing easier for automated tools. However, this causes paths 316 to be difficult to read. 317 </para> 318 <para> 319 You'll notice that registry paths aren't all the same as the 320 equivalents you see in the windows registry editor. This is because 321 Windows constructs the registry view from multiple registry files, 322 each with their own roots. This utility merely shows what exists 323 under a single root. This isn't really a bug, but one should be 324 aware of the differences in path. 316 to be difficult to read by mere mortals. 317 </para> 318 <para> 319 For more information on registry format details, see: 320 http://sentinelchicken.com/research/registry_format/ 325 321 </para> 326 322 </refsect1> … … 350 346 but WITHOUT ANY WARRANTY; without even the implied warranty of 351 347 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 352 GNU General Public License version 2for more details.348 GNU General Public License version 3 for more details. 353 349 </para> 354 350 </refsect1> … … 357 353 <title>SEE ALSO</title> 358 354 <para> 359 reglookup-timeline(1) 355 reglookup-timeline(1) reglookup-recover(1) 360 356 </para> 361 357 </refsect1>
Note: See TracChangeset
for help on using the changeset viewer.