- Cleaner, more modular code
- Better documentation of the code
- Better handling of binary data types
- Translation (i.e., "decrypting" Rot-13 encoding) of UserAssist Registry key value names
To run the script, simply use a command-line similar to this:
C:\Perl>perl regp.pl [path to Reg file] > regp.log
For example, I have a couple of raw Registry files in C:\reg, so my command line looks like:
C:\Perl>perl regp.pl C:\reg\software > regp.log
As with the earlier version, this file is also easily compiled into a stand-alone executable for Windows systems.
Be forewarned...this script will take a while when being run against the "Software" file...the one that holds the HKLM\Software hive. This is due in part to the fact that the Classes key is HUGE!
The next step for me with this project is to complete a script that will allow the investigator to search for arbitrary Registry keys and values. It's been challenging so far, but I've got a pretty good handle on it, so hopefully I'll be able to post something soon.
A couple of final notes...
1. Testing has been limited, as I have only a limited number of VMWare images to pull test files from.
2. This script is intended for raw Registry files (ie, system32\config\software, system32\config\system, ntuser.dat) from NT/2K/XP/2K3 systems.
3. I haven't tested this script on Linux systems, because I don't have regular, unimpeded access to such systems. I am trying to get some things tested on a Mac, but that's someone elses machine.
4. If things don't work as expected, please feel free to let me know. When you do that, though, please give me as much info as you can. I received on email from someone who said that things "looked wonky"...I have no idea what that is. Can you send me the output file, and maybe post the file you ran the script against somewhere (i.e., on a web or FTP site??)? That would be helpful in troubleshooting.