Repository navigation
Replies: 4 comments
|
That path is actually a useful clue. That said, I wouldn't just whitelist it because the filename looks right. 18/70 detections is worth checking. I'd make sure Jasna came from the official release, then compare the DLL's SHA-256 with the copy in the original release package. You can get it with:
Do you still have the VirusTotal report link? The names of the engines flagging it would be useful too. If the hash matches the official package and the detections are heuristic, a false positive becomes much more likely. |
|
I've downloaded jasna from here, the GitHub. https://www.virustotal.com/gui/file/fe1a8cbec15f1be315ea040f443c283c5c3389d5f50eb1b8a470cdc6d1ec81ee Thanks for your support... |
|
The same question came up on another forum, so I compared the file with the PyPI wheel that v0.12.2 pins ( The difference is a single byte at offset So @Kruk2, can you confirm the ASLR flag is a deliberate build step? |
|
Yes, that's on purpose. The build turns on ASLR for every DLL that ships without it, so libtcc.dll differs from the triton-windows copy by that one flag. The hash matches the release, so it's a false positive. TinyCC is a small compiler and antivirus tools flag those a lot. |

Uh oh!
There was an error while loading. Please reload this page.
After downloading jasna 0.12.2 (Windows, nvidia) I got a trojan warning for \triton\runtime\tcc\libtcc.dll
Screenshot from VirusTotal (18/70):

What can I do? Is it a false detection?
Thanks.
All reactions