Re: Learn how to protect your Intellectual Property in this free AHK webinar
Posted: 23 Nov 2019, 09:35
You Bet! Glad to be of help!
Let's help each other out
https://www.autohotkey.com/boards/
https://www.autohotkey.com/boards/viewtopic.php?f=17&t=64565
You Bet! Glad to be of help!
As of Jan 2020, does anyone know if there a good pathway to obfuscate and/or encrypt source code in compiled scripts?your developed script does not have to remain Open Source
I don't quite understand how you have never found an answer to that question, when a search for encrypt or obfuscate will turn up lots of posts on the subject. Probably the latest help topic where the subject was explored is here (and lists some protection options)-freespacing wrote: ↑21 Jan 2020, 23:57As of Jan 2020, does anyone know if there a good pathway to obfuscate and/or encrypt source code in compiled scripts?your developed script does not have to remain Open Source
Last time I looked, about a year ago, I spent three days chasing black cats down blind alleys.
Asking about something that can work with large scripts, with many thousands of lines, lots of include files, tons of functions.
Of course I found lots of threads at the time, that's what I meant in my OP by
Some of these solutions worked only for small files; or required that you compile an alternate version of AHK with an old version of Visual Studio that didn't play well with mine; or that you pepper your script with directives — just not doable for a really large project.I spent three days chasing black cats down blind alleys.
The thread you supplied is more recent: thank you very much, I will look at it. The latest in obfuscation / encryption: that's exactly what I was looking for.1. Obfuscate the code before compiling.
2. Don't try to convert the EXE using tools like MPress: (i) false virus warnings, (ii) published decompiling tools
3. Obfuscation: no success for the large script with the YuHei tool, (ii) trying Autohotkey-Obfuscator-L which is a complex project.
4. Encryption at compilation time: apart from the MPress comment above, there is a tool by HotKeyIt that runs on the branch of AHK calls AHK_H and which requires compiling the AHK_L source code in Visual Studio 2015 (didn't manage it), providing an encryption password.
That same old story: https://en.wikipedia.org/wiki/Open_sourcealfred0809 wrote: ↑10 Jun 2020, 06:53doesnt only ahk itself have to stay open-source? where does it say anything about scripts written for ahk having to be open-source?
There's no reason why our scripts have to stay open-sourced.alfred0809 wrote: ↑10 Jun 2020, 06:53doesnt only ahk itself have to stay open-source? where does it say anything about scripts written for ahk having to be open-source?