← BACK TO SECURITY & TRUST
// POST-CHECKOUT ONBOARDING :: OS GATEKEEPER & SMARTSCREEN GUIDANCE

OS Gatekeeper, Authenticode & SmartScreen Verification

Our software runtimes ship as bare-metal PE32+ executables (justified_engine.exe), Windows installers (justified_engine_setup.msi), Linux ELF64 binaries (justified_engine), and macOS Mach-O arm64 binaries compiled directly from native MSVC, GCC, and Clang toolchains. They contain zero telemetry wrappers, advertising code, or background updater bloat.

AUTHENTICODE HARDWARE HSM ATTESTED • DIGICERT RFC 3161 TIMESTAMPED
// WINDOWS 10 / 11 INITIALIZATION PROCEDURE

Windows Defender SmartScreen Verification

Because raw native runtimes bypass multi-megabyte commercial retail installer wrappers and operate under our private HSM-backed enterprise root authority rather than a retail consumer CA, Windows Defender SmartScreen attaches an NTFS Mark-of-the-Web (Zone.Identifier = 3) to browser downloads. This displays an "Unknown Publisher" prompt upon initial launch:

STEP 1 When the blue "Windows protected your PC" modal appears, click "More info".

STEP 2 Verify the publisher signature reads "CLIGetDefaultPolicy" (Thumbprint: 379A208A4223EE53525B0BBAE9FC4A7FCE76DE9C) and click "Run anyway".

Instant Terminal Unblock Protocol (PowerShell): Developers downloading via terminal (Invoke-RestMethod / curl) or unblocking local builds can strip Zone Identifiers across all binaries with one command:

# 1. STRIP NTFS MARK-OF-THE-WEB ZONE IDENTIFIERS: Unblock-File -Path .\justified_engine_setup.msi Unblock-File -Path .\justified_engine.exe Unblock-File -Path .\justified_core.dll # 2. AUTHENTICODE HARDWARE SIGNATURE VALIDATION: Get-AuthenticodeSignature -FilePath .\justified_engine_setup.msi | Format-List Get-AuthenticodeSignature -FilePath .\justified_engine.exe | Format-List Get-AuthenticodeSignature -FilePath .\justified_core.dll | Format-List # 3. CRYPTOGRAPHIC SHA-256 INTEGRITY AUDIT (CANONICAL PRODUCTION RELEASE): Get-FileHash -Path .\justified_engine_setup.msi -Algorithm SHA256 # Expected MSI SHA256: 8F7DD61DD9C1D33BA8073FC6A61DCA956F5106E7340389F85595E7B0EE7B2084 # Expected Engine SHA256: 1E99ED8F420B2FFCECC196BE00BA51F4352ED167E203B6C3601E2EAF31A9A9C5 # Expected DLL SHA256: 882456EEEFC5FE0BF304E4A358FC9798A915396BAD656A20337F5762E48ACDA0 # Target Subject: CN=CLIGetDefaultPolicy | Thumbprint: 379A208A4223EE53525B0BBAE9FC4A7FCE76DE9C
// CROSS-PLATFORM CLEARANCE :: MACOS & LINUX

macOS Gatekeeper & Linux POSIX Permissions

On Apple Silicon macOS (Sonoma 14+) and enterprise Linux environments, browser downloads apply quarantine flags or omit execute permissions by default:

macOS Apple Silicon (Quarantine Flag Removal):

If macOS blocks execution due to ad-hoc compilation flags, remove the quarantine attribute in terminal:

# Remove Apple quarantine attribute from CLI binary and dynamic library: xattr -d com.apple.quarantine ./justified_engine xattr -d com.apple.quarantine ./libjustified_core.dylib chmod +x ./justified_engine # Terminal downloads via curl automatically bypass macOS Gatekeeper quarantine: curl -O https://justified-systems.com/api/v1/download?target=mac_eval

Linux POSIX ELF64 (Execution Bit Allocation):

Grant user execution rights to the ELF64 binary and dynamic library:

# Set executable permissions on Linux runtime: chmod +x ./justified_engine ls -l justified_engine libjustified_core.so # Execute healthcheck probe: ./justified_engine --healthcheck
// ENTERPRISE IT WHITELISTING & ROOT DEPLOYMENT

Enterprise Group Policy & WDAC Deployment

Enterprise administrators deploying across restricted Windows 10/11 Enterprise environments can deploy our pre-compiled Windows Defender Application Control (WDAC) XML policy directly to authorize our cryptographic signing certificate across enterprise endpoints without manual per-machine prompts.

# Deploy WDAC XML policy via PowerShell (Admin): Set-RuleOption -FilePath justified_wdac_policy.xml -Option 3 Merge-CIPolicy -OutputFilePath Deploy.cip -PolicyPaths justified_wdac_policy.xml