What's new
By:

wLaunchELF MECHAEmu: Access your COH-H10020 security dongles from retail hardware!

Last edited:
CIV initialization vector value generated by using the following Java code.. is it correct way to generate it?

import java.security.SecureRandom;
import javax.crypto.spec.IvParameterSpec;
import java.security.NoSuchAlgorithmException;
import java.util.Arrays;

public class MyClass {
public static void main(String[] args) {
try {
SecureRandom sr = new SecureRandom();
byte[] iv = new byte[8]; // 8 bytes
sr.nextBytes(iv);
IvParameterSpec ivSpec = new IvParameterSpec(iv);

// iv init vector values
System.out.println(Arrays.toString(iv));

// Clean up
java.util.Arrays.fill(iv, (byte) 0);
} catch (Exception e) {
System.err.println("Error generating IV: " + e.getMessage());
}
}
}
 
Jinyong Kim said:
CIV initialization vector value generated by using the following Java code.. is it correct way to generate it?

import java.security.SecureRandom;
import javax.crypto.spec.IvParameterSpec;
import java.security.NoSuchAlgorithmException;
import java.util.Arrays;

public class MyClass {
public static void main(String[] args) {
try {
SecureRandom sr = new SecureRandom();
byte[] iv = new byte[8]; // 8 bytes
sr.nextBytes(iv);
IvParameterSpec ivSpec = new IvParameterSpec(iv);

// iv init vector values
System.out.println(Arrays.toString(iv));

// Clean up
java.util.Arrays.fill(iv, (byte) 0);
} catch (Exception e) {
System.err.println("Error generating IV: " + e.getMessage());
}
}
}
Click to expand...
That's not gonna work.

The Challenge IV vector is always the same, regardless if you're using retail, developer, arcade or prototype magicgate.

I'm not sure if posting it here as is is ok, if any moderator sees this, please answer to the thread
 
Last edited:
civ.bin
Right-click on a blank space on your Windows desktop to create a new txt document, copy and paste the following content: [MODERATED] and save it. Finally, rename the file to civ.bin. You will get civ.bin.
 
Last edited by a moderator:
new update to the DONGLEBINDER ELF (Yes, I know that program is shit, a more flexible alternative, preferrably lua scripted, should be made, but i'm kinda busy and tired. Just in case someone with the skill wants to play around, source code lives here https://github.com/israpps/system2x6-dongle-dumper/tree/dongbind

What's new on this untested update?

Before binding the boot.bin, kbit and kc will be transplanted with the unbound vectors that some of you guys already know (ref: clean_kbit / clean_kcon buffers on source code) to the file before binding.

What's the bennefit? it makes the program capable of properly rebinding boot.bin files that were already bound to a dongle.

It is important to mention that such thing is possible ONLY on arcade mechacons because they expect a fixed decrypted value for both kbit and kc, making copy paste of a fixed vector a valid thing
 

Attachments

You must log in or register to reply here.
Back
Top