v5.1 Working Codes Black Box Initiative

[bitSync]

There was a proposal a little while back to accumulate pairs of working 5.1 unlock codes + ESNs from volunteer d8b owners and to take those pairs and do some sort of enlightened mathematics on them to be able to recover the algorithm to reliably produce working 5.1 unlock codes from ESNs (are there other variables?). Did that go anywhere? Anybody here smart enough to know if that's possible and how large a data set would be required to develop the algorithm from the code/ESN pairs?

I don't have my d8b EULA handy; is there any sort of licensing restriction preventing d8b owners from disclosing their code/ESN pairs?

[topdiggy2]

Who cares at this point...the board is discontinued, unsupported by the manufacturer, and in theory your EULA is null and void.

In the grand scheme of things i don't believe Mackie cares too much about going after a handful of guys playing with 20 year old products.....IMHO

[bitSync]

Who cares at this point...the board is discontinued, unsupported by the manufacturer, and in theory your EULA is null and void.

In the grand scheme of things i don't believe Mackie cares too much about going after a handful of guys playing with 20 year old products.....IMHO

OK, the EULA might not be an issue. But this wasn't my main question. I was looking for some status on the initiative to develop the unlock code algorithm from known pairs of ESNs and unlock codes.

[topdiggy2]

okay, i see...that is the more imporatant issue...lol

[bitSync]

okay, i see...that is the more imporatant issue...lol

Can you actually help me with my question or are you just having some fun?

[doktor1360]

okay, i see...that is the more imporatant issue...lol

Can you actually help me with my question or are you just having some fun?

Bitsync... here's where I kinda left this (because I don't have working codes):

• ESN == 3 groups of 4 digit hex values (ie 0000-01a8-6d9c)
• Mackie then takes these and returns a Box ID in an email with the authorization web page link
• Box ID == 5 groups of 4 alpha character values (ie NXPD-EAVD-XWSX-GMIP-HDGN)
• You then enter your ESN in the provided textbox and 'submit' the page
• A confirmation page is displayed, with your Authorization / Unlock Code in bold (ie 27A8-A189-CB4F)

It's a good bet the auth.asp page logic hasn't been modified (IMHO), but the process for generating those Box ID's is what me thinks is corrupt, and something no one has any knowledge of outside of Mackie (imagine that!).

But in the Bigger Picture, it appears there are TWO conversions:

• from ESN -> Box ID (some ?!?unknown?!? process execution @ Mackie)
• from Box ID -> Authorization / Unlock Code (auth.asp)

That Box ID generated by Mackie certainly appears to be the Fly in the Ointment...

You knew it was coming, so here it is:
[Standard Mgmt Disclaimer] - "Your actual mileage may vary..."

Hope this helps...

Peace

[bitSync]

@dok,

Thanks very much for this. This is exactly what I was trying to hunt down.

Would additional pairs of working codes / ESNs improve your circumstances, maybe at revealing the Box ID algorithm?

[anyhorizon]

The box ID doesn't need the ESN number. It is essentially just a serial number so that Mackie can identify that one has legitimately purchased the product. It is required along with the ESN for authorisation codes to be generated, however.

Peter

[bitSync]

@dok,

I actually have a known good 3-tuple (ESN, Box ID and Unlock Code) for one of my 5.1 machines. I could submit the ESN and see if Mackie comes back with the same Box ID I got when I originally purchased 5.1. That might solve a tiny bit of mystery. Thanks.

[anyhorizon]

Hello.