I've been told that Altmer plans to add support in the OperaFS[De]Compiler for signing images.
The day we've all been looking forward to could be upon us

Plissken wrote:Great news!
They bruteforced it or detected the algorythm?
Maybe... Eventually... But at this point, who the hell knows if I'll actually get that far?oldskool wrote:Uh.. so what does all this mean in English?
Homebrew?
Code: Select all
4C F9 5E 9B 42 6D 06 44 42 FD 55 6E 72 6D B2 F8
1F E9 B8 72 7C DE 52 8E B3 38 8F D3 9C 25 99 B4
DF 8E EE 20 14 45 E9 9F C2 03 DF DD C8 71 5B CD
9F BF 0C FE 2B 36 1F A4 E3 89 06 33 75 C8 77 E2
Code: Select all
75 9C 2D 11 4A CC 74 F6 D7 66 F1 5B 36 4A C4 01
87 20 F2 00 01 77 0A E6 E8 40 28 5E E7 B1 B3 03
76 A8 4E B3 2F 7B E3 80 8A 2A 46 8B EA 21 5D 4C
C4 08 88 6D EA 77 D7 11 7D 46 5F AE 9F C0 3E E8
Code: Select all
FE 5B 22 29 C7 82 BD 04 E6 80 DE 55 CC 23 87 25
Code: Select all
Test.bin fe5b2229c782bd04e680de55cc238725
Code: Select all
57 C8 26 F3 00 44 D9 F6 83 08 D4 AE A6 F2 01 72
A2 B1 1B 0D 10 39 36 0A 05 C6 B1 4D 0D 36 49 D7
43 01 AC C3 22 44 E7 23 80 7D DE 62 8B 94 91 8A
FE 23 12 FA 4F D1 85 FF 1A 53 7C 51 DC D5 33 96
The first target is taking a working disk, and writing all of the values, and comparing it against the original.3DO Experience wrote:Orbatak might not be the best test since it is possible that it would look for the special hardware for the controls.
I know it works in the emulator but it is just an emulator. I have a copy of just obit in iso from before the homebrew disc came out it you want that. You can PM me and I'll give it to you.
cdoty wrote:I'm able to generate a working key for the disc_label rom_tags and boot (This is the 64 byte value stored at 0x900 on the homebrew/game guru disks).
It's simply a matter of combining:
First 0x84 bytes of the cd image (disc_label)
The table located at 0x800 on the cd image (rom_tags). This variable length and ends with a 32 byte section of 0's. On the homebrew image it's 0x100 bytes long.
The code located at 0x1000 (boot_code). The first line of the rom_tags specifies the length (starts with 0x0F 0D 02 05). The length of the data is the 4th 32 bin value in the line (0x176C).
Combining all of this data give you a file that is 6384 bytes long.
The md5 value of this file is attached to the string "1ffffffffffffffffffffffffffffffffffffffffffffffffffffff003020300c06082a864886f70d020505000410"
So you end up with 1ffffffffffffffffffffffffffffffffffffffffffffffffffffff003020300c06082a864886f70d020505000410e787304693b23647f594d901c827f5f6
The "e787304693b23647f594d901c827f5f6" is the md5 value from the homebrew disk.
Then you calculate s = m^d mod n
m = 1ffffffffffffffffffffffffffffffffffffffffffffffffffffff003020300c06082a864886f70d020505000410e787304693b23647f594d901c827f5f6
d and n are from the first key.
s then goes after rom_tags (at 0x900 in the homebrew image).