What's new

Updates are checked for our signature before they install, and updating from inside the app works again.

Security

• Before installing an update, NetSecWall checks that the installer is signed by the same publisher as the copy you are running. An installer that is unsigned, signed by anyone else, or changed after signing is refused and deleted, and the message says which.
• The same check applies to updates pushed by a Management Server.
• The update prompt names the publisher it verified.

Fixed

• NetSecWall closed unexpectedly the moment an update finished downloading, before it could be installed. Versions 1.1.0 and 1.2.0 have this fault, so they are no longer offered updates from inside the app: to move to 1.2.1, download it from this site and run it. Your settings, history and licence are kept.

Managed devices (Enterprise, beta)

• The console can end an isolation it started ("Release"). An isolation that the policy itself requires stays until the policy changes.
• A command this version of the app does not act on is reported to the console as skipped, not as done.

Family and Pro leave beta, the installer is signed, and every list comes from our servers.

New

• Family and Pro are out of beta.
• The installer, the app and the uninstaller are signed, so Windows shows the publisher at the permission prompt.
• Blocklists, category lists and the GeoIP tables are downloaded from NetSecWall's servers on every plan. If our copy of a list is unavailable the app falls back to the list's public source.
• A licence key can be entered in the app again: Help, Sign in to NetSecWall, "Have a license key?".
• Uninstalling asks whether to delete your settings, history and downloaded lists as well. A silent uninstall keeps them unless /PURGE=1 is passed.

Fixed

• Signing in from the app failed when the website's bot check was switched on. The app now opens a one-time check in your browser instead.
• First run opened several dialogs on top of each other. It now shows the welcome screen, then the setup wizard.
• Accented characters and dashes in the welcome screen were garbled.
• Tabs a plan does not include could still be selected by accessibility tools.
• The sign-in window could be taller than a small screen.