Skip to content

ConfigForge v0.3.104

Pre-release
Pre-release

Choose a tag to compare

View all tags
@ABMFST ABMFST released this 28 Oct 05:44
v0.3.104
bcac375
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

ConfigForge 0.3.104 - Windows and Linux

This maintenance release packages the merged security updates and clearer
customer documentation since v0.3.103.

Changed

  • Start with a download and your first saved baseline; advanced deployment
    and packaging remain optional. The guides distinguish benchmark coverage,
    device Audit, and exported Audit Packs.
    (#142)
  • Creating Azure Machine Configuration packages requires the
    Microsoft.OSConfig PowerShell module 1.4.10 or later on the packaging
    machine    , separately from the PowerShell 7 runtime and GuestConfiguration
    toolkit. Follow the packaging guide.

Security

  • Ship the dependency updates, including Electron 42.11.18,
    DOMPurify 3.4.17, and js-yaml 4.3.2. Address the newly reported sanitizer
    bypasses and Electron certificate mitigations before publication.
    (#131,
    #140)
  • Preserve public-asset safeguards and publish SHA-256 manifests and a
    CycloneDX software bill of materials for each platform. Development-only
    dependency advisories remain tracked separately; this is not a claim that
    the entire development dependency tree is advisory-free.

Downloads

Platform Recommended download Alternatives
Windows x64 ConfigForge-Setup-0.3.104-x64.exe Portable .zip
Linux x64 .AppImage .deb, .rpm, or .tar.gz

Use the matching SHA256SUMS-windows.txt or SHA256SUMS-linux.txt to verify
download integrity. Apple Silicon users need the separate
macOS Author release.

Important limits

ConfigForge remains an experimental, community-maintained prerelease,
not an officially supported Microsoft product and not intended for production
use. Downloads are unsigned. Checksums establish file integrity, not
publisher identity or safety. Follow your organization's software policy.

Authoring needs no CLI, administrator access, or Azure subscription.
Optional local device operations require the separately installed compatible
oscfg CLI and appropriate permissions. Existing baseline data is not
automatically replaced by bundled template updates. Back up your work before
upgrading; test packages and enforcement on disposable machines.

Full changes

Assets 15
Loading