- choosenim update stable
- Updating stable
Downloading Nim 2.2.2 from nim-lang.org
- [##################################################] 100.0% 0kb/s
- Extracting nim-2.2.2_x64.zip
- Error: Unable to extract. Error was 'Unable to complete the operation because the file contains a virus or potential malware
- ... '.
I don't know the details why, I'm not a huge windows user, but I read on the discord server that this always happens when compiling nim with mingw, and it seems to subside when doing so with other toolchains (I heard about doing it working fine with zig cc)
Maybe it could be an interesting experiment to try and see if releases built with a different toolchain do not raise such issues
Since this happens again and again (and again :) ), would it be a viable option to start signing the executables? This might build a reputation for the signer and we finally can download (official) nim executables on Windows.
I know nothing about executable signing to be honest. Does someone has some clue?
Looks like there's hope:
Apparently, signpath does this for FOSS