Mike i think it did it to me again... whatever.. good to see you mike, ive been doing alot of work on the program but ive taken a break, in part to think about the new opening UI i want to create, and also im taking time off from work and vacationing, September should be much more productive.
to touch on the
A/V issues and to give insight as to how i build the executable:
----To reduce size the autoit script is only Obfuscated using /striponly, no renaming or tricky script protection.
----The executable it packed using PECompact, this is basicly UPX but not opensource, so the resulting executable is less likely to be detected as a virus
----A stipped down version of winvnc.exe is also (seperatly) compressed with PECompact
----Nothing has digital signatures
it might be worth testing a build that has a non compressed winvnc.exe, i suspect heuristics dont like a compressed executable unpacking and executing another compressed executable from itself that establishes a network connection so quickly.
i just
uploaded 4 builds, the first CAPS is what i did to winvnc.exe and second is what i did to the compiled autoit exe UVNC-Helper.exe (note that by signed i mean that i didnt do ANYTHING to it), also note the size, the largest file should be the least likely to be blocked, and the smallest would be the most likely.
http://teammc.cc/uvnc/more
marcgistel this is impossible as far as i understand, if it were possible it would mean that UAC doesnt work/has a security flaw
but when in the office you can specify allow rules
