Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Daniel explains, that the Antivirus software check the game and finds the launcher, which's job is to detect if you have a 32 or 64 bit computer and launch the corresponding arx.exe.
Quote: The file with almost all of the "detections" is the arx.exe in the root directory, which is a 196 KiB stub executable that detects the host architecture and then runs either bin/x86/arx.exe or bin/x64/arx.exe. The largest part of this file is the embedded icon - there are only 536 bytes of executable code in this file, which should be small enough for anyone interested to disassemble.
Here is the source code, which is probably "causing the issue":
https://github.com/arx/ArxPackages/blob/master/scripts/launcher.c
If it is as you say, the game install looking for client architecture, then like a lot of software available, there is a 32-bit and 64-bit versions for download. Perhaps AL cannot easily be parted out, or some other code reason, but hopefully not just file hosting reasons.
Also have to ask, do you have an estimate for the percent of 32-bit clients using AL is?
Sadly I don't have stats on how many people are playing Arx on a 32 bit machine, but I assume it's less, than 10%
Yes I was concerned as well getting the AV alert from browser then Win Def, but searched online to my satisfaction and enjoyed the game virus/trojan free. But most panic and do not bother to use forum search, or can't effectively.
The devs really should have just released two versions 32- and 64-bit and let client decide which to install, rather than one version and the installer sniff detect the system, which <guessing> is likely the culprit. Other software does not b/c it has gone thru the win certification process which assume is a time and money thing.
I'm chatting with the devs on IRC which you can follow along through the logs, I'll be quoting from there: https://arx-libertatis.org/irclogs/2022/%23arx.2022-10-23.log
1.2 was whitelisted, so whatever caused 1.2.1 to not pass through have been introduced earlier. Checking through the reports and what is being marked as SUS or unsafe you can find nonsense, like marking the readme as ransomware because it contains the following text: Copy the data (.pak files and misc and graph directories) from a fully patched Arx Fatalis 1.21..or 1.22 install into this directory to use them with arx and arx-portable
( source: https://www.joesandbox.com/analysis/685670/0/html )
The reason why I posted here is that I like (AF and) AL, and I would like this Trojan issue to be resolved once and for all - after all, most other game mods don't have such a problem at all. I suppose the mod developers know why browsers and AV software complain about AL 1.2.1, and unless the reason is critical for AL to be working, it should be possible to modify AL accordingly. Correct me if I'm wrong.
So it is totally fine to expect a software to be marked as safe, but with so many false positives it's very hard to know what to change.
@Ionetrav: does Norton have any issues if you download the portable version which contains a zip file with exe files instead of downloading the installer? (link: https://arx-libertatis.org/files/arx-libertatis-1.2.1-windows.zip)
I won't try to unzip the file on the PC I'm using right now - perhaps on a different one tomorrow,
Try downloading this and run this through Norton to see if this gets any threats detected. Arx can be executed with this by running bin/x86/arx.exe or bin/x64/arx.exe
Thanks for your help - and I hope I could help you to identify the issue(s), too.