I thought they may be useful for others so I'm posting them here if anyone would like to use em. These use the DLLs from the official IsoTools (1.34.9). If new IRD versions come out you should be able to just copy the DLLs from the new IsoTools into this directory and they should still work (as long as the API doesn't change). Requirements are the same as IsoTools, .NET Framework 4.0. Also it is probably best not to upload the Redump>IRDs to 3k3y, even though they should be identical (*possible caveats, see end section).
BIN: http://www.mediafire.com/?a778vbvivq8b91a
SRC: http://www.mediafire.com/?816184so6npkam9
Share Folder: https://www.mediafire.com/folder/xp4a51jifjs66/PS3Tools
Tools
Redump2IRD.exe: Generates an ird file from a redump PS3 ISO.
PS3IRDToMD5.exe: Will create a .md5 file from an ird. Has command line support.
PS3IRDCleaner.exe: Will make the JB directory files match the size the IRD specifies by truncating/appending/creating 0's. WARNING: PS3IRDCleaner modifies files in the JB directory, use with caution (ideally on copied JB folders).
Let me know if anyone notices any bugs or issues, or needs better documentation to use. Thanks.
Changes
2014-07-27: Updated bins/src so the Redump2IRD program has cancellation logic. It also has a "Redump Mode" checkbox (on by default) which makes it hard to get the AES ENCRYPTED/AES DECRYPTED fields mixed up for redump iso's (turning the checkbox off puts it in the old/advance mode). And it now remembers the ird/iso folder locations you last used if you make multiple IRDs.
Caveats
* Last 8 bytes of BD-25 D2 decrypted data is random, redump lists as X's (ie 00000000000000FF00020003XXXXXXXX) while IsoTools seems to replace the end eight bytes with "00000001". The program will automatically replace redump X's with 0000001.
* 3k3y pic data for BD-50 ps3 discs seem to have the last byte (byte 115) of pic data replaced to "03". If you are attempting to make exact 3k3y IRDs then for BD-50's take redumps PIC data and replace byte 115 with 03 when providing it to Redump2IRD (note BD-25 discs don't have this replacement). PIC data is not used for the 3k3y rebuilding logic, so this is more-so cosmetic for most users. IE:
Redump BD-50 Disc (note the bold):
10020000444901100000200042444F01
210103000000000001EC8DDF00100000
00CA73FE000000000000000000000000
00000000000000000000000000000000
00000000444901110001200042444F01
210103000000000001EC8DDF01358C00
01EFFFFE000000000000000000000000
00000000000000000000000000000000
000000003k3y BD-50 Disc (note the bold):
10020000444901100000200042444F01
210103000000000001EC8DDF00100000
00CA73FE000000000000000000000000
00000000000000000000000000000000
00000000444901110001200042444F01
210103000000000001EC8DDF01358C00
01EFFFFE000000000000000000000000
00000300000000000000000000000000
00000000
Notes
* Redump is storing D1/D2 in a 'processed' state (some other programs use the term 'decrypted'). This means the final version of redump's D1 is aes encrypted, and the final version of redumps D2 is aes decrypted. This is useful for figuring out where to put redump data in the Redump2IRD.exe program which uses the terms 'aes decrypted/encrypted' (new 'Redump Mode' checkbox added to the program on 2014-07-27 as well which makes it easier to figure out which field is which).