Windows Defender and openmsx beta builds

Page 2/3
1 | | 3

By Bengalack

Resident (62)

Bengalack's picture

01-03-2020, 17:45

I get the same "error". Chrome does not let me try to even look at the file (Norwegian settings in browser):

By Manuel

Ascended (16158)

Manuel's picture

01-03-2020, 22:15

So, what can we do about this, folks?

By Bengalack

Resident (62)

Bengalack's picture

08-03-2020, 09:54

An update on this. I have downloaded the src-files and built from that on windows 10, using latest Visual Studio Community 2019 (v16.4.4).

When building the file, windows puts the exe in quarantine right away. I now calls the threat something else than mentioned in OP. Norwegian output, but it states that it is "serious":

OS-name: Microsoft Windows 10 Home
Version: 10.0.18362 Build 18362

I am able to restore it now, but am I safe? Would be nice if someone could look into this, as, going further, this will surely hinder the widespread of this fantastic tool.

Last, I'm not an expert on this, but given "Trojan"-classification, could it be that Defender is triggered by the fact that openmsx is possible to control remotely? And that there is a flaw in that part of the code that can be abused by external threats? In some of the libs that are used?

By sdsnatcher73

Paladin (809)

sdsnatcher73's picture

08-03-2020, 10:56

Again my mingw64 build does not trigger Windows Defender... Maybe it is an idea to start using GitHub Actions to build these development (as well as release) builds? I found some info here https://techcrunch.com/2019/08/08/github-actions-is-now-a-ci...

By sdsnatcher73

Paladin (809)

sdsnatcher73's picture

08-03-2020, 12:49

If you are interested, I have successfully implemented staticbindist build for Linux and Windows using GitHub Actions in a personal fork: https://github.com/peterhanraets/openMSX

Currently it builds I still have to add artefact upload.

By Manuel

Ascended (16158)

Manuel's picture

08-03-2020, 13:26

Bengalack wrote:

Last, I'm not an expert on this, but given "Trojan"-classification, could it be that Defender is triggered by the fact that openmsx is possible to control remotely? And that there is a flaw in that part of the code that can be abused by external threats? In some of the libs that are used?

Then why wouldn't it also trigger on a MinGW build?
What happens with older versions of openMSX, which have the exact same capability?

I have the strong suspicion that this is a false positive. But I have no idea what to do about it. It should simply be possible to build and use openMSX, as you want (Visual Studio, MinGW, etc.).

By FiXato

Scribe (1555)

FiXato's picture

08-03-2020, 14:55

I'll also see if I can use the Virus-Total API to determine from which build this started being an issue.

If the Continuous Integrations through GitHub Actions works and is free as in gratis, then I'd say that is an interesting alternative, especially if macOS can also be supported.

By sdsnatcher73

Paladin (809)

sdsnatcher73's picture

08-03-2020, 15:39

FiXato wrote:

I'll also see if I can use the Virus-Total API to determine from which build this started being an issue.

If the Continuous Integrations through GitHub Actions works and is free as in gratis, then I'd say that is an interesting alternative, especially if macOS can also be supported.

It is possible to build on MacOS (yes build ON MacOS, not just for!): https://help.github.com/en/actions/reference/virtual-environ...

By sdsnatcher73

Paladin (809)

sdsnatcher73's picture

08-03-2020, 18:21

So I managed to build Linux, Windows (mingw) and macOS using GitHub Actions and create a zip file (or use the created dmg) which is uploaded as an artifact, I think it should be possible to use e.g. a REST call to openmsx.dev with the artifact's URL so the site can be updated automatically. It now caches the 3rd party dependencies between builds, not sure if this is a good idea (can be removed easily of course). If you guys like it just copy the 3 .yml files from .github/workflows into the official repo.

The windows build could be improved to build the msi using the linux tool msi-packager.

By Manel46

Hero (524)

Manel46's picture

08-03-2020, 19:07

I just installed the latest version for w64 with the msi, without any problem.
I am with w7 / 64. My antivirus is Norton, to which I am subscribed. I pay the annual fee.

Page 2/3
1 | | 3