98w ago - Today Spanish PlayStation 3 developer
JaicraB has explained the Cobra USB JIG protection RTOC trick implemented for the PS3 against cloning the device.
To quote, roughly translated: Flynn sent me this text explaining this protective carrying the Cobra, I hope it will open the eyes of those interested in reversing the dumps.
EXPLAIN RTOC COBRA TRICK
The JIG Cobra has several protective measures to ensure that your code could not be used correctly even if your code could be dumped.
This trick RTOC in the registry is the first used for this purpose in addition to hinder analysis.
Registration is initially RTOC stored in the battery to keep the RTOC of lv2 and power it back later:
# =============== S U B R U T I O N E
cobra_syscall_sm_shutdown_hook: # CODE XREF: j syscall_379
. Arg_20 September, 0x20
. Arg_28 September, 0x28
. Arg_30 September, 0x30
. Arg_38 September, 0x38
. Arg_40 September, 0x40
mflr% r0
std% r0, arg_20 (% sp)
std% RTOC, arg_28 (% sp)
At this point we have to explain that the OFFSET DELTA. DELTA OFFSET is a method used in the x86 in its original moments in the creation of computer viruses, to calculate the memory address in which we are in the sea of bytes in RAM.
In the original time a computer virus when I did not know where he was pulled into an executable,
depending on the executable it could be an initial site or another, for it was invented DELTA OFFSET.
DELTA OFFSET can be used in any system, the procedure is:
- Using the record that indicates the current execution address (or the next depending on the system)
- Reducing the size of the previous code we use the value obtained from the registry.
Knowing this, and taking for example the x86 processor where the EIP register can not be read directly invented the trick make a call to a "subfunction" which is simply the following line to the call:
X86 call instruction saves the top of the stack the address of the next instruction to itself. Thus using pop draw from the top of the stack this value, and stored in eax for example, and having the memory address where we only subtract the above would be missing and we have the exact calculation.
The PowerPC can use this trick using the BL instruction is equivalent (LINK BRANCH), which jumps to a "subfunction" but before you save LR in the record the following address to BL.
_delta_offset bl
_delta_offset:
At this point we see the trick used for the creation of the RTOC of charges at this time. If you look both r0 and RTOC are passed to 0:
Subsequently, given the value 0x11DE0 to RTOC:
RTOC oris%,% RTOC, 1
RTOC ori%,% RTOC, 0x1DE0
A r0 is given the value 0x920:
oris% r0,% r0, 0
ori% r0,% r0, 0x920
R0 is subtracted from the value of RTOC:
Unlike the PowerPC x86 LR register can be read directly with mflr instruction, we put in RTOC the value obtained by the delta offset:
To calculate the delta offset subtract final instructions executed before the delta offset, which were 4, or 16 bytes:
Finally we add the value of r0 at the end of the delta offset RTOC, storing the result in the RTOC and this already takes RTOC suitable for this hook:
It takes having the RTOC stored in the stack 3 arguments that the hook received:
std% r3, arg_30 (% sp)
std% r4, arg_38 (% sp)
std% r5, arg_40 (% sp)
You call the function of the charges where the first argument will check for command 0x8202 (a special command to the usual):
cobra_syscall_sm_shutdown bl
After making the necessary steps as charged, the battery recovers the original RTOC, like the arguments the hook received, it executes the original instruction that was overwritten in the syscall entry 379 (in this case) to have our hook, and call the original syscall lv2:
ld% RTOC, arg_28 (% sp)
ld% r3, arg_30 (% sp)
ld% r4, arg_38 (% sp)
ld% r5, arg_40 (% sp)
mfcr% r12
original_syscall_sm_shutdown bl
Upon returning to retrieve the original LR from the stack and returns to the prompt
ld% r0, arg_20 (% sp)
mtlr% r0
blr
# End of function cobra_syscall_sm_shutdown_hook
No
Are you Depressed?...
Download: http://www.sendspace.com/file/x6qtvr (725.67 KB)
• bdRESET6
• gameDATA6
• lastGAME6
• stDISC4
All support: 3.55 CEX/DEX, 4.21 CEX/DEX, 4.30 CEX/DEX, 4.31CEX, 4.40CEX. These four tools are also available in mM's WEB column.
Download: http://www.sendspace.com/file/8qkcl5 (109.04 KB)
Contains modified source and PS3 executable "ps2classics.self". It can be used by any PS3 application to convert a regular disc PS2 ISO to ISO.BIN.ENC.
Can be used as easy as:
char* launchargv[8];
memset(launchargv, 0, sizeof(launchargv));
launchargv[0] = (char*)malloc( 2); strcpy(launchargv[0], "e");
launchargv[1] = (char*)malloc( 4); strcpy(launchargv[1], "cex");
launchargv[2] = (char*)malloc(i3); strcpy(launchargv[2], klc_path );
launchargv[3] = (char*)malloc(i1); strcpy(launchargv[3], iso_path1);
launchargv[4] = (char*)malloc(i2); strcpy(launchargv[4], iso_path2);
launchargv[5] = (char*)malloc(12); strcpy(launchargv[5], "ISO.BIN.ENC");
launchargv[6] = (char*)malloc(37); strcpy(launchargv[6], "2P0001-PS2U10000_00-0000111122223333");
launchargv[7] = NULL;
_Exitspawn(ps2classics, (char* const*)launchargv, NULL, NULL, 0, 1001, SYS_PROCESS_PRIMARY_STACK_SIZE_1M);
Where iso_path1 is the source iso, iso_path2 is the destination encrypted iso.bin.enc and klc_path is the path to the klicense.
I just tested it (launching a regular ISO in mM, it spawns the ps2classics.self and creates the encrypted ISO + a folder structure) - everything seems ok. It needs a nice progress bar, improved I/O by using async read/write and you're good to go. It doesn't support 4GB+ files, but properly adds missing info for CD ISO files.
Basically with mM you can dump your PS2 game disc, load it in the RETRO column, it will convert it to ps2classic in a minute or two and you can load it with ps2-classics-placeholder. I'll release a test mM later.
Showtime 04.03.128 by Andreas Oman is now available (for mM and as standalone in the WEB column).
Download: http://www.sendspace.com/file/wwrggi (5.68 MB) / http://www.sendspace.com/file/q7hgg0 (5.74 MB)