Skip to content

SecReview 0.2.0

Latest

Choose a tag to compare

@github-actions github-actions released this 14 Nov 09:03
Immutable release. Only release title and notes can be modified.
v0.2.0
b531251

Install

Download SecReview-0.2.0-setup.exe and run it. For a silent install: SecReview-0.2.0-setup.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART.

SHA-256: 570db89eeed12b48530f874f3ac61685446c03cee918e14195ec7ac7a3a6ba4c

SecReview-0.2.0.spdx.json lists what is installed and the packages it was built from (SPDX 2.2).

Both files were built by this repository's workflow. To verify:

gh attestation verify SecReview-0.2.0-setup.exe --owner CadworkNA --bundle SecReview-0.2.0.sigstore.json

What's Changed

Changes

  • fix: the signing module and its tools are checked by SHA-256 before they run by @jspaquet in #50
  • fix: the update address is written in the release workflow, not in a repository variable by @jspaquet in #51
  • fix: administrator checks read BitLocker without the shell and need a protected install folder by @jspaquet in #52
  • fix: keep the answers with and without administrator rights side by side by @jspaquet in #55
  • feat: 51 hardening rules from the Windows 11 26H2 security baseline by @jspaquet in #57
  • fix: a log line written while the log is busy is no longer lost by @jspaquet in #61
  • feat: more places for the credential and trust checks by @jspaquet in #60
  • test: the posture test weakens what the credential and trust checks look at by @jspaquet in #62
  • build: one commit builds to the same files, except the window program by @jspaquet in #63
  • docs: the repository is public; what checking the helper from a release takes by @jspaquet in #66
  • docs: README with badges, the releases and the newer checks by @jspaquet in #67
  • docs: Best Practices answers give the URLs the site requires by @jspaquet in #68
  • docs: OpenSSF Best Practices badge, passing by @jspaquet in #69

Full Changelog: v0.1.1...v0.2.0