Open Makazzz opened 5 years ago
Probably because this tries to upload telemetry to 0.0.0.0
and the Microsoft URLs are allowed in the anti-malware software.
Probably because this tries to upload telemetry to
0.0.0.0
and the Microsoft URLs are allowed in the anti-malware software.
But why it is doing that only in the ia32 version? I have no problem with the x64. My settings.json is this : { "telemetry.enableTelemetry": false, "telemetry.enableCrashReporter": false, "update.channel": "none", "update.mode": "manual", "update.enableWindowsBackgroundUpdates": false, "update.showReleaseNotes": false, "workbench.enableExperiments": false, "workbench.settings.enableNaturalLanguageSearch": false, "extensions.autoUpdate": false, "git.ignoreMissingGitWarning": true, }
Microsoft force enables telemetry anyway. I'd blame it on Windows.
Pretty weird situation @Makazzz -- I will try to reproduce it on my Windows machine and figure out what exactly it is reacting to. Thanks for reporting!!
Is the windows binary codesigned? Distribution windows binaries without (preferably EV certificate) is world of hurt, as everything flaggs it as malware. And even with certificate there are still often heaps of false positives.
The Windows binary is not being codesigned at this time. I should prioritize that if it would help with malware false positives.
Information: I can't test this problem anymore because I uninstalled Bitdefender.
@stripedpajamas wrote:
The Windows binary is not being codesigned at this time. I should prioritize that if it would help with malware false positives.
It definitely would. Ideally both the executable and the installer exe+msi would use the same code sign
Just adding the reference: #527 (already closed, but found first in my search).
@daiyam Closed, so the installer and executables are now signed?
no, I've closed it because of "False positive Malware"
Then the "old issue of signing the codium executable and the installer (however this may work) is still open, I'd suggest to keep track of code signing certificate issues here.
reopening it to keep track of code-signing here.
Each time I open VSCodium ia32 in portable mode on a Windows 10 x64 with Bitdefender; It's saying Atc4.detection or Malware detected and block it.
-[✓] This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.
-[✓] I checked the Docs page and my issue is not mentioned there.
To Reproduce Steps to reproduce the behavior: