Skip to content

SecureWall v0.3.0 (alpha, unsigned installers)

Pre-release
Pre-release

Choose a tag to compare

View all tags
@ryanportfolio ryanportfolio released this 13 Sep 18:02
v0.3.0
5385cab
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

SecureWall v0.3.0

This is an unsigned alpha prerelease for exploratory testing. It includes the firewall hardening and optional diagnostics added since v0.2.0. It is not signed or end-to-end verified.

Changes

  • Strict external blocking during service loss and startup, with hardened policy recovery, service validation and protected machine-data handling.
  • A saved Enable diagnostic logging checkbox under Settings > General, off by default.
  • Detailed service, policy, blocklist, hosts backup/restoration, DNS, audit, attribution and recovery observations. The read-only collector reports missing evidence, incomplete operations and recorded failures.
  • Removed the inactive automatic-update checkbox and global hotkeys. Manual exception editing remains available.
  • TinyWall .tws import remains available. Import loads the whole saved configuration, including allow/block rules and other settings. Enable diagnostics after importing an older export.

Downloads and installation

Use SecureWall_x64.msi on Intel/AMD 64-bit Windows, SecureWall_arm64.msi on Windows on ARM, or SecureWall_x86.msi on 32-bit Windows. Verify the download against SHA256SUMS.txt. All installers are unsigned.

Remove TinyWall and reboot before installing SecureWall. Existing SecureWall installations require full removal before installing this version; in-place upgrades and repair are unsupported. Keep local console access and recovery installers available offline. Service loss can leave external networking blocked, including DNS and DHCP.

Collect a diagnostic report

Read the live testing guide and coverage map. Download the source archive for this tag to obtain tools/diagnostics, or use a checkout of this tag. Run the collector with Windows PowerShell 5.1 as described in its README. It creates a local report and does not upload it.

Logs record software outcomes and observed filtering decisions. They do not prove packet delivery, absence of boot/crash leakage, installer rollback, hostile filesystem resistance or power-loss durability. The bundled blocklists do not automatically update. Review normal-use logs before drawing conclusions about live behavior.

Assets 6
Loading