Skip to content

KATAI 2D v0.7.1

Choose a tag to compare

@fkkarakurt fkkarakurt released this 09 Aug 21:23
· 49 commits to main since this release

KATAI 2D v0.7.1

Packaging release. No engine change: the same solver, the same results, the
same verification record (150 automated tests, 45 declared verification cases).
If v0.7.0 runs for you, there is nothing new to compute here.

Why this release exists

The v0.7.0 Windows executable shipped with an empty version resource — no
product name, no version, no publisher, no copyright. That is poor practice on
its own, and on a binary that is also unsigned and newly published it is what a
reputation heuristic reads as anonymous: Microsoft Defender flagged
katai2d-0.7.0-win64.zip as Trojan:Win32/Wacatac.B!ml and removed it.

Wacatac.B!ml is a generic machine-learning label, not an identification of any
known malware — the !ml suffix says the verdict came from a heuristic. The
downloaded file's SHA-256 matched the published checksum exactly, so what was
flagged was this project's own build, unmodified.

What changed

  • The executable now declares its product name, version, publisher, copyright
    and origin
    , generated at build time from version.hpp, so the binary's
    Properties tab cannot drift from what katai info prints. The rebuilt
    executable and its zip both scan clean.

That is a mitigation, not a guarantee. An unsigned binary from a project with no
download history can be flagged again by any engine, and the honest answers are:

  • Verify what you downloaded. Every release publishes a SHA-256 beside each
    asset:
    (Get-FileHash .\katai2d-0.7.1-win64.zip -Algorithm SHA256).Hash.ToLower()
  • Get an independent opinion if you want one: the assets are public, so
    uploading one to VirusTotal discloses nothing private.
  • Use the wheel, which has never been flagged:
    pip install katai2d-0.7.1-cp312-abi3-win_amd64.whl.
  • Code signing is on the roadmap; it is the only real fix for the underlying
    reputation problem, and it is a purchase, not a patch.

The detection has been reported to Microsoft as a false positive.

Assets

File What it is
katai2d-0.7.1-win64.zip Self-contained command line for Windows: one executable, no runtime dependency, Eigen solver backend. Smoke-tested with PATH scrubbed to C:\Windows\System32.
katai2d-0.7.1-cp312-abi3-win_amd64.whl Python package (pip install), CPython ≥ 3.12, with the katai console script. Verified in a fresh virtual environment.
*.sha256 Checksums, also used by install.ps1.
katai2d-0.7.1-win64.zip
  7112f4784ee2f6dd1154f183e9d50de91fece59a5e62f8db41d732b8caca7faf
katai2d-0.7.1-cp312-abi3-win_amd64.whl
  572f1c8a2ba1d4b8d6e37472d8c4e75ed29c9da67803e221c5150741e3c7edb5

What is in 0.7.0, if you are coming from 0.6.x

Ten inputs a geotechnical model needs and could not express — wells and drains,
a wall that blocks water, rainfall boundaries, anchor prestress, per-phase water
conditions, Undrained (C), per-material undrained stiffness, a dilatancy
cut-off, a staged-construction target and per-phase numerical controls — plus
the diagnostics that stop an input from being discarded in silence, and a
numerical uncertainty band for published numbers. See the v0.7.0 notes.