You have to use as awkward key names as possible, but still, it is avoidable with parameters, as my functions are written. A global key is dangerous: somebody might try to use that variable for something else. If it is nonzero, perform encryption, otherwise decryption (and this way there is no need for the markers around the IV). IfWinActive, ahkexe SciTE.exe replace with the path to your gui creator 1::Run, 'D:ScriptsAHK Gui Creator. I would instead add an extra parameter, default to 0. If you want the super easy way, make this into a script or add it to your main script (if you have one). Also, global variables are confusing, error prone and considered bad style. So the user needs to include only one function? But it will be slower, having an extra if statement in the innermost loop, or larger than the two original functions, if you separate the code for encryption and decryption. But, why do you want to bring these into one function and control it with global variables? You have to choose one policy in your unified function: with or w/o markers around the IV. There are two flavors of the scripts I posted: The control/selection encryption uses markers around the IV, because its presence indicates, that we have encrypted text (and so plaintexts must not start with _ 8-digit hexnum/_).Įn/decrypting AHK variables don’t need this, because there are separate functions for encryption and for decryption. Would it be too much asked to build in a pass/passphrase to hash conversion, to get the 128-bit key? Maybe with help of the RC4 script by Rajat? 1 - get pass/passphrase e.g.

Domain name choosing is important to maximize search engine-referred traffic. A human-memoribility domain name length should be maximum chars of 9 as well as brand-friendly.

Decrypt max script editor commands