For those wondering as to why the code was so basic in the API, it's just that I plan to improve on it by a lot in future parts, and simply cannot fit it all in this one :)
amazing video! i'd only recommend to zoom in when any buffer is on screen, either in the edition or while recording, . the letters should be readable in the standard video size on youtube, even tho nothing really useful is showing, i feel that small fonts on videos about programming is a huge deal. . take care and keep going
Is my understanding of this topic correct: The loader itself doesn't need to be packed / obfuscated (except for the decryption functions (would still help to do the rest of the loader to make it harder to find decryption funcs)) you only need to decrypt the encrypted DLL thats going to be requested. The DLL sent back from the server must be encrypted with your HWID, license key, and time (subscription duration) and the DLL must not land on disk ever, only in memory. This raises a question, if the person who is attempted to crack the cheat, there would be at one point, the unencrypted DLL. This leads to me ask, does the DLL also need to have checks within itself? Eg, serveral hwid checks, several time checks and several license checks? (one check is not enough) I do remember someone telling me these functions should vary as if they are the same, all instances of the function could easily be found and patched out.
I will cover this subject in a future part, but yes you should encrypt the binaries you fetch from the server and make it hard to reverse engineer the steps of decryption which lead to execution. I wouldn't make the DLL check these things itself, but instead have a hidden stub do it.
Please subscribe 😢
Sorry you’re getting a lot of leachers man :( you’re doing great work
@@Xmw92ba3oenalfk9 ♥
For those wondering as to why the code was so basic in the API, it's just that I plan to improve on it by a lot in future parts, and simply cannot fit it all in this one :)
Awesome video! Also, your editing has really improved!
Thanks ♥
Bro holy shit. You are a legend. Learned cheat development because of you. Amazing tips! Big love
Really glad for that, thanks for the feedback ❤
Amazing video man the thumbnail is so cool!!
Thanks haha but it’s @kapitcheGHT who made it !
amazing video!
i'd only recommend to zoom in when any buffer is on screen,
either in the edition or while recording,
.
the letters should be readable in the standard video size on youtube,
even tho nothing really useful is showing,
i feel that small fonts on videos about programming is a huge deal.
.
take care and keep going
True, I should take care of making the font bigger in the future
nice video! i had a similar approach when i tried making my own loader!
Cool
bro you are so underrated wtf
Haha thanks mate!
Good job brudda ❤
Thanks bro and also I think people like your thumbnails haha!
Damm, underrated asf
Thanks 🙏
Subbed even though im nnot yet at the skill to follow. But im learning
That’s what matters the most !
nice, though we all know true hackers only use CLI with green text
Haha I agree !
Is my understanding of this topic correct:
The loader itself doesn't need to be packed / obfuscated (except for the decryption functions (would still help to do the rest of the loader to make it harder to find decryption funcs)) you only need to decrypt the encrypted DLL thats going to be requested. The DLL sent back from the server must be encrypted with your HWID, license key, and time (subscription duration) and the DLL must not land on disk ever, only in memory.
This raises a question, if the person who is attempted to crack the cheat, there would be at one point, the unencrypted DLL. This leads to me ask, does the DLL also need to have checks within itself? Eg, serveral hwid checks, several time checks and several license checks? (one check is not enough) I do remember someone telling me these functions should vary as if they are the same, all instances of the function could easily be found and patched out.
I will cover this subject in a future part, but yes you should encrypt the binaries you fetch from the server and make it hard to reverse engineer the steps of decryption which lead to execution. I wouldn't make the DLL check these things itself, but instead have a hidden stub do it.
Authentificate?? xd
Yeah yeah, very funny my English sucks :(
Awesome video ! Now I'm gonna paste allat bro
Paster