-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Unable to work on Windows 11 due to detected trojan virus #48
Comments
It's not a Trojan. If I were to guess, Defender sometimes identifies it as such due to the self-updating functionality. What's more frustrating is that it only sometimes screams about it, not consistently. You may just need to whitelist it. This problem will likely come and go until MS and other vendors see Tauri apps more frequently. The only permanent fix in the meantime is probably to sign the executable using an EV code signing certificate... but that costs hundreds of dollars per year to maintain, which is not an investment I can feasibly make at the moment. |
Funnily enough, it seems nothing improperly flags the MSI version of the installer with anything, according to a VirusTotal scan - so if you'd rather not whitelist anything, you can give that a shot. Also on the subject of VirusTotal, according to the scan on the EXE installer, nothing is detected in behavioural analysis. It's purely some signature-based AV that is being tripped. |
I just released v0.4.0 and scanned both the installer and the installed EXE manually with Defender, but it didn't report anything this time around. Dunno if it's just a fluke or if it's actually okay with this version, but I didn't make any relevant changes. |
I tried the EXE installer for v0.4.1 and it worked and didn't warn me about a trojan. So maybe this issue can be closed? Although the problem may still crop up again in future releases. |
Most recent 0.8.0 still appears to have this issue for some. According to VirusTotal, it is still being flagged by one vendor along with matching a yara rule on Resolute/crates/resolute/src/manifest.rs Line 20 in b3cae91
|
Trojan:Script/Wacatac.B!ml
The text was updated successfully, but these errors were encountered: