Error when upload x86 compiled exe to Github repo - (Moved)

[hudsonhock]

Hi, I bump into an error when uploading any x86 compiled exe into Github repository.

The problem remain the same across different browser (Chrome & Edge).

Currently Github only accept my x64 compiled exe but x86, but surprisingly, it accept other x86 exe (portable application).

This is really weird! I had asked in Github community and they don't believe in x86 structure restriction which is true because other x86 portable application is being accepted.

In this case, I think I might need to add something in my script but not sure. Has anyone bump into this?

Edited May 30 by hudsonhock

[Melba23]

Moved to the appropriate forum.

Moderation Team

[hudsonhock]

Thanks Melba for moved it to appropriate forum.

I did some experiments as following:

• turn the code scanning in Github to none
• zip or change the extension of the exe
• using x86 compiler to compiling x86 and x64 (tick x64 option)
• using x64 compiler to compiling x86 (untick x64 option) and x64 (I supposing this step has no different to the above step)

It turns out that the end result remain the same, Github see something wrong on my x86 compiled exe.

From this point, I might need to consider an alternative to Github where I can store my .exe applications, and able to download the .exe applications (or be it any file extension such as .txt) by going to the link just like in Github. Can anyone who has sort of solution that may suggest if nothing I can do about on the compiled .exe before upload to Github?

[argumentum]

I don't do Github but a file .exe on the net may benefit from a zip w/password. Say, "123" as a password. Try it and see if that solves the issue. Because if is not github removing it, it'll be the browser while downloading.

[hudsonhock]

Github still reject the x86 exe even I zipped it. I've tried Chrome, Edge and Firefox to no avail.

But surprisingly, I tried on a laptop with Win10 and Github accepted the file without any issue. But the file flagged by Defender for having Trojan.

A stupid question: Can we add any extra code on top of the script such as it declare the script/file come in peace without any harm?

 

[argumentum]

1 hour ago, hudsonhock said:

Can we add any extra code on top of the script such as it declare the script/file come in peace without any harm?

You can sign your exe. That will help, but just help. So I guess no. If the file gets downloaded by millions of people then the good fame will remove it from defender, I think.   

Edited June 4 by argumentum

[hudsonhock]

Thanks for your suggestion @argumentum That's probably the legit solution to this, I mean a proper one. I will do the search for it and see how it goes.

[hudsonhock]

I found out the error is due to Zscaler (It’s a bundle of security services. ZScaler Internet Access proxies your Internet traffic and runs it through URL content filter lists.). Basically it detects my x86 exe having trojan thus it restricted the upload.