Upcoming Ahk2Exe Changes (2024)
Re: Upcoming Ahk2Exe Changes (2019)
@lexikos Is the uppercase crucial or can that be changed without issue?
Windows 10 x64 Professional, Intel i5-8500, NVIDIA GTX 1060 6GB, 2x16GB Kingston FURY Beast - DDR4 3200 MHz | [About Me] | [About the AHK Foundation] | [Courses on AutoHotkey]
[ASPDM - StdLib Distribution] | [Qonsole - Quake-like console emulator] | [LibCon - Autohotkey Console Library]
Re: Upcoming Ahk2Exe Changes (2019)
Simple test: open some executable in Resource Hacker, try to add anything - say a text file - as RC_DATA and see how the resource name appears. Delete the name and try typing lowercase. Draw a conclusion.
Part of my AHK work can be found here.
- JoeWinograd
- Posts: 2203
- Joined: 10 Feb 2014, 20:00
- Location: U.S. Central Time Zone
Re: Upcoming Ahk2Exe Changes (2019)
Interesting point...hadn't thought of that.gregster wrote:so, heuristically your exe might look more risky than others to them, right from the start
Good call! I tried it with one of my real programs...no problem! Went through the same procedure with the same code as I had used in HelloWorld...no detection this time.Drugwash wrote:However, variations on "Hello world" may well be on the black list; have you tried other more sensible names in the Manifest?
I do submit my Setup.exe files to VT and recently submitted a false-positive report to one of the A-V products that VT flagged. I was stunned to get the following reply:Drugwash wrote:You may submit your exes to VirusTotal for analysis
Hello and thank you for submitting. Your case 12345 has been closed. The submitted content was confirmed to be a false positive and will be fixed in an upcoming definition update.
Yes, I put a section in all my user guides/manuals called "Anti-Virus/Anti-Malware False Positives". I mention VirusTotal in the section and even have a couple of quotes from them, including this beauty: "False positive detections are common in the antivirus industry. They occur when a benign program is wrongfully flagged as malicious due to an overly broad detection signature or algorithm used in an antivirus product." Even so, it still spooks a lot of users...besides, who reads the doc?Drugwash wrote:also mention that option in a ReadMe file and/or other places related to the distribution of your exes
Yes, found that out during my first test with a real program...used upper and lower case...no joy...but I'm fine with all upper case.lexikos wrote:I think that resource names with lower-case letters don't work (maybe for specific APIs or situations?).
Thanks to everyone for all the feedback. Regards, Joe
Re: Upcoming Ahk2Exe Changes (2019)
I tried a null-terminated string, but the compiled exe couldn’t find the embedded script, whereas space-filling to the original size worked.
My scripts:-
XRef - Produces Cross Reference lists for scripts
ReClip - A Text Reformatting and Clip Management utility
ScriptGuard - Protects Compiled Scripts from Decompilation
I also maintain Ahk2Exe
XRef - Produces Cross Reference lists for scripts
ReClip - A Text Reformatting and Clip Management utility
ScriptGuard - Protects Compiled Scripts from Decompilation
I also maintain Ahk2Exe
- JoeWinograd
- Posts: 2203
- Joined: 10 Feb 2014, 20:00
- Location: U.S. Central Time Zone
Re: Upcoming Ahk2Exe Changes (2019)
A quick update to let you know that I switched two of my programs to Beta_7 using many of the SetProp directives, UpdateManifest (to replace name and version), AddResource (to replace the 160, 206, 207, 208 icons), and PostExec with BinMod (to replace the RCData entry). Everything worked perfectly on both programs. I used NSIS to create a Setup.exe that included the EXE from each Beta_7 compile and both the installer and the installed program ran on W7 with no detections by MBAM or MSE, and on W10 with no detections by Defender. Great job by TAC109 and everyone who helped! Regards, Joe
Re: Upcoming Ahk2Exe Changes (2019)
@JoeWinograd
I’m pleased it’s working out for you!
I’ve found another use for BinMod; to alter a UPX compressed .exe so that it can’t be de-compressed with UPX -d. This will involve a small enhancement to Ahk2Exe, which I’ll get onto after I’ve finished wrestling with GitHub!
I also wish to add the UPX parameter to stop it compressing the icons. This was a request of yours, joe?
Cheers
I’m pleased it’s working out for you!
I’ve found another use for BinMod; to alter a UPX compressed .exe so that it can’t be de-compressed with UPX -d. This will involve a small enhancement to Ahk2Exe, which I’ll get onto after I’ve finished wrestling with GitHub!
I also wish to add the UPX parameter to stop it compressing the icons. This was a request of yours, joe?
Cheers
My scripts:-
XRef - Produces Cross Reference lists for scripts
ReClip - A Text Reformatting and Clip Management utility
ScriptGuard - Protects Compiled Scripts from Decompilation
I also maintain Ahk2Exe
XRef - Produces Cross Reference lists for scripts
ReClip - A Text Reformatting and Clip Management utility
ScriptGuard - Protects Compiled Scripts from Decompilation
I also maintain Ahk2Exe
- JoeWinograd
- Posts: 2203
- Joined: 10 Feb 2014, 20:00
- Location: U.S. Central Time Zone
Re: Upcoming Ahk2Exe Changes (2019)
Interesting idea! I had been unaware of the -d option on UPX until you mentioned it earlier in this thread. Would be very nice if it weren't so easy to de-compress a UPX.I’ve found another use for BinMod; to alter a UPX compressed .exe so that it can’t be de-compressed with UPX -d.
Yes, I mentioned that, because when I experimented with UPX, RH showed only Group 159 in the EXE, and after creating a shortcut to the EXE and doing Properties>Change Icon on the shortcut, it said that the file contains no icons. lexikos then pointed out that it's due to the compression of resources, which occurs along with the compression of the script text. At that point, I mentioned that I decided to stick with MPRESS, which was working well with AddResource (for the icons) in Beta_7. I've gone back and forth over the years with MPRESS versus UPX, but lately (since UPX v3.95, 26-Aug-2018) have had fewer false positives with MPRESS. Would certainly be happy to give UPX another try if you can prevent -d from de-compressing. Thanks, JoeI also wish to add the UPX parameter to stop it compressing the icons. This was a request of yours, joe?
Re: Upcoming Ahk2Exe Changes (2019)
i've been submitting my setup.exe's to AV vendors for years, and it usually works, they update their definitions. the problem is, they only seem to whitelist an individual file, instead of doing some actual research and figuring out the heuristic. that means with each new setup.exe version, i had to re-submit it againJoeWinograd wrote: ↑31 Oct 2019, 13:06I do submit my Setup.exe files to VT and recently submitted a false-positive report to one of the A-V products that VT flagged. I was stunned to get the following reply:Hello and thank you for submitting. Your case 12345 has been closed. The submitted content was confirmed to be a false positive and will be fixed in an upcoming definition update.
i typically used this page:
https://www.techsupportalert.com/content/how-report-malware-or-false-positives-multiple-antivirus-vendors.htm
- JoeWinograd
- Posts: 2203
- Joined: 10 Feb 2014, 20:00
- Location: U.S. Central Time Zone
Re: Upcoming Ahk2Exe Changes (2019)
Good to know...I was wondering about that. I update my software fairly often (most of my programs have a Check for Update menu pick), so having to submit each updated Setup.exe file is a real pain, but I'll certainly do it.guest3456 wrote:the problem is, they only seem to whitelist an individual file
Thanks for that link! I was unaware of the ability to submit false positives to multiple A-V Vendors at once...very nice!guest3456 wrote:i typically used this page
Btw, I wasn't ignoring your earlier suggestion about AutoHotkey_H. I downloaded it to try, but ran into problems with both MBAM and MSE (see attached files). I was thinking about whitelisting it, but got very concerned about moving forward with it when I saw this post:
https://www.autohotkey.com/boards/viewtopic.php?f=65&t=68608#p295278
I'm fine with explaining away to my users 2 or 3 false positives out of 60+ vendors, but 22 makes it a whole different ballgame (and I create a 32-bit version of all my programs). So, I decided not to pursue AutoHotkey_H further, combined with the fact that the main AutoHotkey branch with TAC109's Ahk2Exe (and MPRESS) is working well now. Regards, Joe
- Attachments
-
- AutoHotkey_H-mse-virus-detected.png (52.68 KiB) Viewed 5341 times
-
- AutoHotkey_H-mbam-virus-detected.txt
- (1.37 KiB) Downloaded 128 times
Re: Upcoming Ahk2Exe Changes (2019)
i saw that thread. it is concerning to me too, because i was planning on migrating my software to AHK_H soon (i currently still use AHK Basic so that i can protect my source with the HotkeyCamo compiler).JoeWinograd wrote: ↑01 Nov 2019, 12:44Btw, I wasn't ignoring your earlier suggestion about AutoHotkey_H. I downloaded it to try, but ran into problems with both MBAM and MSE (see attached files). I was thinking about whitelisting it, but got very concerned about moving forward with it when I saw this post:
https://www.autohotkey.com/boards/viewtopic.php?f=65&t=68608#p295278
I'm fine with explaining away to my users 2 or 3 false positives out of 60+ vendors, but 22 makes it a whole different ballgame (and I create a 32-bit version of all my programs). So, I decided not to pursue AutoHotkey_H further, combined with the fact that the main AutoHotkey branch with TAC109's Ahk2Exe (and MPRESS) is working well now. Regards, Joe
an alternative i used for one project was to distribute an AHK Basic wrapper program to my users (protected with HotkeyCamo), which sole purpose was to download an encrypted script txt file from my server, and then i would run that script through ahk.dll - that way i got _L/_H functionality through the .dll, and the executable was just an AHK_Basic file. i may go that route if necessary
Re: Upcoming Ahk2Exe Changes (2019)
Well, I've managed to beat GitHub into submission! As a result, the location for Beta_7 has changed.
Please see the first post on page 1 for the new download address.
Cheers
Please see the first post on page 1 for the new download address.
Cheers
My scripts:-
XRef - Produces Cross Reference lists for scripts
ReClip - A Text Reformatting and Clip Management utility
ScriptGuard - Protects Compiled Scripts from Decompilation
I also maintain Ahk2Exe
XRef - Produces Cross Reference lists for scripts
ReClip - A Text Reformatting and Clip Management utility
ScriptGuard - Protects Compiled Scripts from Decompilation
I also maintain Ahk2Exe
Re: Upcoming Ahk2Exe Changes (2019)
URL shorteners? Never! I wanna see clearly where I'm being sent before getting there.
Not to mention advertising and delays introduced by a possible interim page redirector.
Not to mention the security risk if the shortened link somehow gets hacked and users click it in good faith.
Not to mention advertising and delays introduced by a possible interim page redirector.
Not to mention the security risk if the shortened link somehow gets hacked and users click it in good faith.
Part of my AHK work can be found here.
- JoeWinograd
- Posts: 2203
- Joined: 10 Feb 2014, 20:00
- Location: U.S. Central Time Zone
Re: Upcoming Ahk2Exe Changes (2019)
Congrats!TAC109 wrote: I've managed to beat GitHub into submission!
URL Expander is your friend for this (and clean, according to URLVoid). Using that, the long URL is:Drugwash wrote:I wanna see clearly where I'm being sent before getting there.
https://github.com/TAC109/Ahk2ExeT/releases/tag/1.1.30.03_beta_7
Regards, Joe
- JoeWinograd
- Posts: 2203
- Joined: 10 Feb 2014, 20:00
- Location: U.S. Central Time Zone
Re: Upcoming Ahk2Exe Changes (2019)
Very clever! I never heard of HotkeyCamo. I just went through all 13 pages at this HotkeyCamo thread on the archived forums. I see that yours was the last post there...four years ago! Is there a more recent thread about it? Thanks, Joeguest3456 wrote:an alternative i used for one project was to distribute an AHK Basic wrapper program to my users (protected with HotkeyCamo), which sole purpose was to download an encrypted script txt file from my server, and then i would run that script through ahk.dll - that way i got _L/_H functionality through the .dll, and the executable was just an AHK_Basic file.
Re: Upcoming Ahk2Exe Changes (2019)
@joedf
Joe, I’ve created a fork of Ahk2Exe under TAC109 on GitHub and am editing via my pc to there. I’m having problems pulling to AutoHotkey/Ahk2Exe. I did one and it seems ok, but when I try to do the next it wants to include the first pull! Help!
(Can I message you directly somehow? I couldn’t see how to message on GitHub).
@JoeWinograd
FYI I’m making some changes to Ahk2Exe, including making compression a DLL in the GUI, and sorting out the destination field.
Cheers
Joe, I’ve created a fork of Ahk2Exe under TAC109 on GitHub and am editing via my pc to there. I’m having problems pulling to AutoHotkey/Ahk2Exe. I did one and it seems ok, but when I try to do the next it wants to include the first pull! Help!
(Can I message you directly somehow? I couldn’t see how to message on GitHub).
@JoeWinograd
FYI I’m making some changes to Ahk2Exe, including making compression a DLL in the GUI, and sorting out the destination field.
Cheers
My scripts:-
XRef - Produces Cross Reference lists for scripts
ReClip - A Text Reformatting and Clip Management utility
ScriptGuard - Protects Compiled Scripts from Decompilation
I also maintain Ahk2Exe
XRef - Produces Cross Reference lists for scripts
ReClip - A Text Reformatting and Clip Management utility
ScriptGuard - Protects Compiled Scripts from Decompilation
I also maintain Ahk2Exe
- JoeWinograd
- Posts: 2203
- Joined: 10 Feb 2014, 20:00
- Location: U.S. Central Time Zone
Re: Upcoming Ahk2Exe Changes (2019)
Hmmm...what's the purpose of this?making compression a DLL in the GUI
Sorry...not unserstanding this, either.sorting out the destination field
Re: Upcoming Ahk2Exe Changes (2019)
@JoeWinograd
DLL = dropdown list. ('Compress exe with' in the GUI.)
Destination field on the GUI; There were some problems with the default destination shown when selecting a folder.
Both these were concerns of yours, I believe.
Cheers
DLL = dropdown list. ('Compress exe with' in the GUI.)
Destination field on the GUI; There were some problems with the default destination shown when selecting a folder.
Both these were concerns of yours, I believe.
Cheers
My scripts:-
XRef - Produces Cross Reference lists for scripts
ReClip - A Text Reformatting and Clip Management utility
ScriptGuard - Protects Compiled Scripts from Decompilation
I also maintain Ahk2Exe
XRef - Produces Cross Reference lists for scripts
ReClip - A Text Reformatting and Clip Management utility
ScriptGuard - Protects Compiled Scripts from Decompilation
I also maintain Ahk2Exe
Re: Upcoming Ahk2Exe Changes (2019)
nope, that thread from the old forums is the only one.. that compiler offered decent protected for AHK Basic scripts, much better than just the basic pwJoeWinograd wrote: ↑02 Nov 2019, 18:06Very clever! I never heard of HotkeyCamo. I just went through all 13 pages at this HotkeyCamo thread on the archived forums. I see that yours was the last post there...four years ago! Is there a more recent thread about it? Thanks, Joe
if you don't know what you're doing, you shouldn't be pushing directly to the repo. instead, you should fork into your own account, and then do pull requests from your fork back into the main repoTAC109 wrote: ↑02 Nov 2019, 19:18@joedf
Joe, I’ve created a fork of Ahk2Exe under TAC109 on GitHub and am editing via my pc to there. I’m having problems pulling to AutoHotkey/Ahk2Exe. I did one and it seems ok, but when I try to do the next it wants to include the first pull! Help!
(Can I message you directly somehow? I couldn’t see how to message on GitHub).
edit: ok i just looked, and that's what you're doing already. but PR #59 includes the same file as you already merged with PR #58. the reason is because you are pushing all your changes to the master branch. you shouldn't be doing that. you should be creating a new branch for each new feature, and then doing a pull request from your specific branch into the master branch of the main repo
alternatively, you could re-sync your fork with the main repo, and then push your changes to your master, and then do the PR, and then resync again
are you using git command line on your machine? or are you using the github software?
Last edited by guest3456 on 02 Nov 2019, 20:20, edited 1 time in total.
- JoeWinograd
- Posts: 2203
- Joined: 10 Feb 2014, 20:00
- Location: U.S. Central Time Zone
Re: Upcoming Ahk2Exe Changes (2019)
Got it. Problem is, DLL=dynamic link library. I would have had it with DDL. Yes, that was mine...much better than the tri-state checkbox, imo.DLL = dropdown list. ('Compress exe with' in the GUI.)
Ah, yes, the folder wasn't sticky...that was mine, too.some problems with the default destination shown when selecting a folder
Re: Upcoming Ahk2Exe Changes (2019)
here's what i suggest if you're using the git bash command line:TAC109 wrote: ↑02 Nov 2019, 19:18@joedf
Joe, I’ve created a fork of Ahk2Exe under TAC109 on GitHub and am editing via my pc to there. I’m having problems pulling to AutoHotkey/Ahk2Exe. I did one and it seems ok, but when I try to do the next it wants to include the first pull! Help!
(Can I message you directly somehow? I couldn’t see how to message on GitHub).
with this method, you wouldn't be using separate branches for new features, but rather keeping everything in master branch. so do this on your local machine:
1. git checkout master
2. copy the 2 files from this commit (Ahk2Exe.ahk and Compiler.ahk) and copy them to a separate folder so we can preserve the changes
3. revert your master branch 2 commits to undo your changes with git reset --hard HEAD~2
4. then sync your local machine copy with the main repo with git pull upstream master. this assumes you've set the 'upstream' repo to match github.com/AutoHotkey/Ahk2Exe
5. then drop your 2 files back in and git add and git commit
6. then update your copy on github with git push --force origin master (assuming you've set up 'origin' to match your github.com/TAC/Ahk2exe
7. then your PR #59 should automatically update with only your new single commit
Return to “Scripts and Functions (v1)”
Who is online
Users browsing this forum: No registered users and 78 guests