- by bxaimc at 6:10 PM EDT on April 30, 2017
- At every 0x60 it starts with this xor key: A3DD5146 7C495B1C 81258155 9A6BAFD5
Then the xor seems to change based on the previous -0x10 decoded value?
dec at 0x03 is AF, xor at 0x13 is 91
dec at 0xC3 is AD, xor at 0xD3 is 93
dec at 0x08 is 25, xor at 0x18 is 0A
dec at 0xC8 is 25, xor at 0xD8 is 0A
(values near 0x08 and 0xC8 change, while 25 is fixed )
That's all so far.
Keep note that at3 itself is split up into frame starting with Ax (in this case A2)
- by bnnm at 5:48 PM EST on February 6, 2018
- I gave it another go and managed to decrypt those AT3 files, yay.
I remembered AT3 has 0-frames (=easy keys), and combined with the "value depends on the above" idea I was able to understand what was going on.
Decryptor here, I used python like the fancy kids, it's meh. Video encryption is much more complex btw, guess they had cycles to spare.
Incidentally DoC uses the same filesystem used in FF XIII (you can use the same ff13.bms), most curious.
- by AnonRunzes at 12:36 PM EST on February 8, 2018
- @bnnm - can you see if my .bat attempt is correct?
for %%i in (*.at3) do python doc_at3_dec.py %%i
edited 12:37 PM EST February 8, 2018
- by bnnm at 1:38 PM EST on February 8, 2018
- I think it is? But I just used
for %%i in (*.at3) do doc_at3_dec.py %%i
Btw, the rip I uploaded should have a .bms to extract loop points and create GENHs.
- by AnonRunzes at 1:43 PM EST on February 8, 2018
- ok, i'll guess that'll do for now
HCS Forum Index
Go to Page 0 1
Search this thread
Show all threads
Reply to this thread:
Halley's Comet Software
Generated in 0.0027s;