Repository navigation
Windows Smart App Control blocks bundled signal_jni_amd64.dll in signal-cli 0.14.9 #2158
Replies: 1 comment
|
it's not a known/fixable thing on the signal-cli side right now: the DLL is unsigned upstream. i checked the 0.14.9 tarball: that matches your 3077 event. Smart App Control lets a binary run only if Microsoft's cloud service is confident it's safe or it has a valid signature, and "there is currently no way to bypass Smart App Control protection for individual apps" (Microsoft FAQ). on top of that the JVM extracts the DLL to a fresh heads-up if you push for signing: options that keep SAC on:
|
Uh oh!
There was an error while loading. Please reload this page.
I am using the upstream signal-cli 0.14.9 distribution on Windows x64 with Temurin JRE 25.0.5+8. The distribution SHA-256 was checked against upstream.
The --version command succeeds, but attempting link fails when loading the bundled signal_jni_amd64.dll. Windows CodeIntegrity records an enforcement block, Event ID 3077. Smart App Control is enabled (VerifiedAndReputablePolicyState = 1), although I have not directly matched the enforcing policy name.
Is this a known compatibility issue? Is there an upstream-maintained release with a trusted Windows code signature on the bundled JNI DLL, tested with Smart App Control enabled? If not, is signing planned, or should this be raised against a specific libsignal artifact?
I would like to keep Windows security protections enabled. No account identifiers or linking QR data are included.
All reactions