-
Notifications
You must be signed in to change notification settings - Fork 245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cracking Live.Application.encrypt_challenge2 #36
Comments
What the fuck I did NOT expect a reply, let alone more than 3 years later. Incredible job |
@Reiszecke come talk to us on discord if you'd like, i think we could have an interesting chat https://discord.gg/upSFBwy |
Unfortunately I'm not into all that anymore, I don't even own a push as I am busy covering another field at the moment but I got a few things in mind to get back into it hopefully, let's see what 2020 is gonna look like :) I might join at some point to see how you guys are doing |
All good mate, I'm also on and off working on other stuff, we're sitting in voice right now so uh yeah |
Hey guys, has anyone touched the encrypt_challenge2 yet? The Launchpad Pro script requires it. What's basically happening is the following
So it's taking the note that you send and then adds the next note but shifts it so you end up with a pretty big number. This then runs through the challenge so the response can be compared in order to find out whether or not the connected controller is legit.
My first try would be to run this script for every number there is in order to obtain a lookup table. But it would end up pretty big and might not be the finest solution of them all. Maybe it makes some calculations obvious (e.g. the first byte just gets multiplied by 3 or stuff like that) but am pretty sure they won't make it that simple.
Another way would be to try getting the challenge decompiled but Ableton isn't just a simple Java app with 2 classes - it's pretty much the most advanced DAW I've ever gotten my hands on so I bet there is tons of native code and such in there, probably obfuscated and optimized like nothing else. Idk how long it took to decompile these Python scripts here but I don't think it won't take longer for parts of the Ableton.app.
I do have one or two working handshakes for the old launchpad script and its "encryption" is pretty similar to the one for the Pro BUT the handshakes that I use might have been taken from the very first Launchpad when they maybe haven't implement the challenge yet. (I really don't know)
The only difference is that for the Pro it's bytes[7:8] and for the older one it's bytes[5:6]
Any ideas?
The text was updated successfully, but these errors were encountered: