Skip to main content
SQuin.2
Associate
Apr 14, 2020 7:53 AM UTC
Solved

Avast virus checker tells me that the newly installed STM32CubeIDE is infected (see attached). What should I do?

..

This topic has been closed for replies.
Markus GIRDLAND
Markus GIRDLANDBest answer
ST Employee
Apr 15, 2020 10:54 AM UTC

I’ve sent the request to the developers to also sign the windows binaries for future releases which they say won’t be a problem for future releases because now the ST-LINK GDB server is built separately from the CubeIDE build, which wasn’t the case previously.

We didn’t sign the windows binaries before because they were just a step in the build process and the signing process needs to be done manually.

For now, I would create an exception to allow the file.

So to summarize: It will be fixed in future releases of CubeIDE.

2 replies

Markus GIRDLAND
Markus GIRDLANDBest answer
ST Employee
Apr 15, 2020 10:54 AM UTC

I’ve sent the request to the developers to also sign the windows binaries for future releases which they say won’t be a problem for future releases because now the ST-LINK GDB server is built separately from the CubeIDE build, which wasn’t the case previously.

We didn’t sign the windows binaries before because they were just a step in the build process and the signing process needs to be done manually.

For now, I would create an exception to allow the file.

So to summarize: It will be fixed in future releases of CubeIDE.

SQuin.2
SQuin.2Author
Associate
Apr 15, 2020 11:54 AM UTC
Thank you for a most comprehensive answer Markus.