-
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown publisher / company (Windows Defender block HJT) #22
Comments
Hi, BUBBLEIO! It's not a bug. In order, Ms Defender recognizes new unknown software as safe if it is signed by so called EV (extended validation) certificate. It cost near 400$. Since, personally for me there is no special need to have certificate for one single and freeware software, it's a huge money here in Ukraine. So I don't planning to buy it. Currently, my digital signature is self-signed (mean, self-issued) and can be confirmed in file properties: Here is statistics: https://www.herdprotect.com/signer-alex-dragokas-f4dbdd6e9c3591ac4a5c39e95a82536f.aspx Verification check will fail with error: "A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider." It's normal, and mean binary is successfully passed integrity check, but cert. is not trusted. Alternatively, you can install my certificate in the root storage by clicking file properties -> digital signatures -> Details -> View certificate -> Install certificate... In such case Publisher/Company will be shown in UAC window. Also, every test or public build surely passes VirusTotal check before uploading by default. Since, currently, it's not possible to resolve MS Defender false-positive (in general, for all future binaries), However, after each public release (v.3+) we'll try to send sample to Microsoft. |
OK clear. I wasn't aware of this level of requirement for windows which are NOT a SERVER version. Your position is totally logic. Stay like this... |
I leave this issue open, so, everyone don't ask the same again. |
There must be something wrong. Windows can't run the binary, when downloaded directly. The zipped version contained Trojan:Win32/Spursint.F!cl according to Windows Defender and was removed. And Visual Studio fails to clone while resolving 810/816 deltas. I usually never experience that. And it makes recompiling impossible. There is no problem with 2.0.5 Beta from sourceforge. Consequently, there must be something in the code, which triggers the problem. And surely noone would dare using it for the purpose of getting rid of malware, with such an issue. |
Hi, gywerd!
There is nothing wrong. Windows defender is very suspicious to any new file without valid signature. I can offer to look in VirusTotal instead.
I am not expert in different GitHub stuff. So, I can't answer why this bug happen. I even don't know how to reproduce it. You don't need VS to download the project. It can be downloaded without problems by button "Clone or download" in this page or via git bash. If you are expecting problems when trying to compile my project, please, open new issue and describe in details. Project can be compiled without any problem directly via VB6 IDE (build 9782), launched as elevated (just sometimes need to repair reference to Microsoft MSComCtl.dll), or via 2_Make&UPX&_Sign.cmd file (you will have binary identical to mine (just without my EDS). |
Everybody who accidentally detect the false positives of the antivirus on our HiJackThis Fork, please report to the appropriate antivirus company according to their form or e-mail. Most of them you can find in this topic: https://safezone.cc/threads/kuda-soobschit-o-lozhnom-srabatyvanii-antivirusa.23501/ Or, leave comment in this topic. Thank you. |
Hi,
That's me again...
When I start hijack THE FIRST TIME Ms Defender don't want to start it (red dialog) because the software has 'no publisher / company'. It is presented like a virus. that's not good, in the doubt, users can stop and forget it.
I've seen this behaviour after starting the beta to test bug correction.
Regards,
The text was updated successfully, but these errors were encountered: