Home

software

reg3dit

This one looks like and feels like the popular "Microsoft ® Registry Editor" (A.K.A. regedit.exe Eye-wink), specifically one that comes from Win2k default installation.
It only has one (significative) difference... It will never prompt you with following message box, when started:

"Registry editing has been disabled by your administrator."
"Registry editing has been disabled by your administrator."

This restriction is supposed to save users from themselves. Well, if you've successfully located an override (like mine Smiling), I hope you really know what's you're doing! My regedit clone will ignore administrator's restriction, which consist in the following registry patch:
REGEDIT4

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System]
"DisableRegistryTools"=dword:00000001
Then, you may use reg3dit to make all the changes you need (note that on Windows NT/2k/XP & superiors some keys would still give you "Access denied", as such OSes use per-user security policies). For example, you can unpatch that DisableRegistryTools thing and simply turn back to use default regedit.exe Smiling

P.S. - reg3dit has nothing to do with the leaked Win2k source!!! I've created it by my own.

stas's picture
stas » April 20, 2006 » 01:16
C » database » GUI » hack » software » windows
attachment » 8 comments » 11612 reads

knuckle cracker

This project is a response to the urge to make small changes to the big binary files. For text files, there are diff/patch utilities; and for big changes, rsync is perfect. Now, if  you're sharing something like a game mod, where you need to swap a single bit inside a huge data file (just like in a Hot Coffee Mod for GTA San Andreas Eye-wink, you're frequently forced to share the entire file. By the other side, if you need to update some firmware glitch, why should you rewrite the entire flash chip?! So, here's my proposal.
bin_diff utility will compare two binary files and output a human-readable (and writable Smiling script file, just like this:

[bb35cc23dda6737d181a63ea3203f0ff engine.dll]
50	"This program must be run under Win32\xd\xa$"
d60a	EB
d77b	90 90
da3f	E9
da41	1 0
ea44	90
# Patch length: 0000007A
First line contains a name of the file to be patched, and it's MD5 checksum value. Following lines start with a hex offset inside this file, and the new byte(s) value. Note that strings with C-like escaping style are supported! You may also comment each line, using the hash character (#). Several files may be patched by a single patch-script. The last string in the last line is a hex value of the patch data length. It is useful to make self-applicable patches.
Then, knuckle_cracker may be used to parse the patch-script and apply modifications to the files. It will check the MD5 checksum for each file automatically (and will refuse to patch unmatched files). You can also make the self-applicable patches, concatenating the patch-script directly at the end of the knuckle_cracker executable (following example works on UN*X systems, for Windows box, use any hex editor, it works just the same):
cat knuckle_cracker engine.bin_patch > engine_patcher
Both bin_diff & knuckle_cracker are very portable: I tested them on Linux, FreeBSD (gcc) & Win32 (Borland C/CYGWIN/MinGW/MSVC).

P.S. - all sources has DOS line endings (CRLF), use
"unzip -aa knuckle_cracker.zip" to extract on UN*X systems.

stas's picture
stas » April 19, 2006 » 02:42
C » console » hack » linux » opensource » software » windows
attachment » 6 comments » 17005 reads
XML feed