luarmor.net, as data

03b3b409-f0b97340-40b97304-48327b49827HWID value, same as clienthwid. But "exec-" must be the name of your platform/executor.0391a1e58f324b3a0c79d32dd09436bd45bfc773SHA1 signature. See below for how it's calculated.You must create a random nonce (16 char alphanumeric string) called **clientnonce**, which you'll later reference again to re-calculate server signature. For now, let's hold it in a variable.**How is "externalsignature" calculated?**This ensures that the outgoing request parameters can't be spoofed / tampered with, without replicating the signature, which should be significantly difficult if you obfuscate/virtualize the auth part of your binary.**HTTP Response would look like this:**⚠️You will get a **"signature"** field in the response if the code is "KEY_VALID".For everything else, there will be no signature included. Just simply reflect the error message to the user. It doesn't matter if they spoof anything other than KEY_VALID.See below for response signature validation.**How is KEY_VALID -> "signature" calculated?**You will use this response signature to check if returned KEY_VALID is actually real, and not just coming from a skid's fiddler4 autorespond rule.Rest of your code should look like this:Possible status codes can be found here:Luarmor User Manual & F.A.Q | Luarmor Documentationdocs.luarmor.netBut generally, you're only interested in whether it is "KEY_VALID" or not.Contact f.e.d.e.r.a.l for any questions.PreviousUseful Sample Scripts`const fetch = require('node-fetch');const crypto = require('crypto');// You will be given 3 "shared secrets" by the owner, in DMs.// you'll use them in the SHA1 signature calc in next step.const app_name = "minecraftdlc" // you will be given this too, by federal.let keyToCheck = "BAfjuLxndwTvMBNiCyqMsXMaTcOqXpcr" // user-inputted// random str gen a-z A-Z and 0-9 only. And fixed 16 char output.