Skip to content

Code signing policy

CyberGems edited this page Nov 14, 2026 · 3 revisions

English · Español

Code signing policy

Free code signing provided by SignPath.io, certificate by SignPath Foundation.

What is signed

The following files are code signed through SignPath Foundation:

File Description
CyberWall.exe Application
CyberWall.Service.exe Background service
CyberWall-Setup-vX.Y.Z.exe Inno Setup installer

The portable archive contains the same signed application and service binaries.

Team roles

  • Committers and reviewers: CyberGems, owner and sole maintainer of the repository.
  • Approvers: CyberGems.

Releases are built by GitHub Actions from a tag in CyberGems/CyberWall. The approver creates the tag and approves each signing request manually. No binary is signed from a developer machine or from untagged code.

Signing order

The installer embeds the published files, so the order matters:

  1. GitHub Actions builds and tests the tagged commit.
  2. CyberWall.exe and CyberWall.Service.exe are signed.
  3. The installer is compiled from the signed binaries and then signed.
  4. The portable archive is packaged from the signed binaries.
  5. The release publishes the signed files together with their SHA256.

Artifact metadata

Signed binaries declare the product name CyberWall and the product version from Directory.Build.props. SignPath enforces these attributes through metadata restrictions, and the release pipeline will fail when they do not match.

Privacy policy

The project's privacy policy is the CyberGems Privacy page. In addition, this program will not transfer any information to other networked systems unless specifically requested by the user or the person installing or operating it.

CyberWall has no telemetry, no accounts, no analytics and no crash reporting. It contacts the network only for these features:

  • Update checks: api.github.com (the public GitHub Releases API), enabled by default and can be turned off in Settings.
  • Country flags: a public IP-to-country table downloaded from the jsDelivr or unpkg CDN. Only the public IP addresses already shown in the connection lists are looked up, locally against that table.
  • Connection status: reachability probes to msftconnecttest.com, google.com and 1.1.1.1, used by the online indicator.

Beyond ordinary HTTP request metadata (source IP and the CyberWall user agent), no information about you or your system is transmitted, and the project does not collect or store any of it. Update packages are downloaded from GitHub Releases only when the user accepts an update.

Verification

Get-AuthenticodeSignature .\CyberWall-Setup-vX.Y.Z.exe | Format-List Status, SignerCertificate

A signed build reports Status: Valid, a signer certificate issued to SignPath Foundation, and a timestamp counter-signature. Every release also publishes the SHA256 of each file so downloads can be verified independently.

Current status

CyberWall has applied to SignPath Foundation. Releases published before the project is approved are unsigned and rely on the SHA256 published in the release notes; the antivirus and SmartScreen warnings caused by that are documented in Installation & Setup.

Clone this wiki locally