(Jul 31, 2024, 13:10 pm)Kpucko_10 Wrote: I have cracked version of v2. follow my instagram for info: https://www.instagram.com/kpucko_10/

(Jul 31, 2024, 13:10 pm)Kpucko_10 Wrote: I have cracked version of v2. follow my instagram for info: https://www.instagram.com/kpucko_10/

(Jul 31, 2024, 13:10 pm)Kpucko_10 Wrote: I have cracked version of v2. follow my instagram for info: https://www.instagram.com/kpucko_10/

(Aug 01, 2024, 15:29 pm)el_rafas Wrote: is it safe his instagram?

(May 17, 2024, 17:36 pm)jackberalta Wrote: I am halfway through crack.

I have managed to reverse engineer the server-side licensing using other valid keys from flight factor itself. I intercept the response from license server which says you have entered an invalid license code and I am replacing the response with a valid one which you get by using a valid key for another product. 

Eg. you buy 757 legit, so you get the response you get from activating 757 legitimately and send that for 777 instead

The problem is SASL or whatever license lock system is here is downloading an aircraft specific file from the license. 

Eg. If you use the response to activate 757 for 777, you will get message that activation is successful and it will ask you to reload the plane, but when you reload the plane it asks for activation again.

This is because when you activate 777 with 757 response, it will download a main.key file that is vital to make the plane work, but it is only made for 757. Therefore it will give error when we try and use it with 777. There is no point activating like this

If we can get legit main.key file which is already activated with legit 777 code, I can reverse engineer license server and make it so that we can activate the b777 as many times with any sort of random license! but without this file i am not sure what to do.

other files i would need to access to experiment with and see what is going on (eg. win.xpl or initMain.secured files in sasl folder in b777 plugin is all encrypted i think but i don't know what encryption)