v2.3.1

What's Changed

• Remove references to a function removed long ago @mikeytdisco (#76)
  
  Change Details

    ## Description

  Code comments and the library DfciUiSupportLibNull reference a function no longer used. This removes the dead code from the NULL library, and updates comments in the active code. Fixes #75

  For each item, place an "x" in between [ and ] if true. Example: [x].
  (you can also check items in the GitHub UI)

  • Impacts functionality?

  • Impacts security?

  • Breaking change?

  • Includes tests?

  • Includes documentation?

  How This Was Tested

  Not tested

  Integration Instructions

  N/A

    </blockquote>
    <hr>
  </details>
  

• Fix duplicate name error when adding second firewall rule @mikeytdisco (#73)
  
  Change Details

    ## Description

  Originally tested on a system where the firewall was disabled, so the missing firewall entry error was not observed. Fixes #74

  • Impacts functionality?

  • Impacts security?

  • Breaking change?

  • Includes tests?

    • Changes the setup script

  • Includes documentation?

  How This Was Tested

  Tested configuring a Windows Guest running in a QemuQ35Pkg VM.

  Integration Instructions

  N/A

    </blockquote>
    <hr>
  </details>
  

🐛 Bug Fixes

• DfciPkg/DfciMenu: Fix memory leaks @wenbhou (#66)
  
  Change Details

    ## Description

  Fix #65

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

  How This Was Tested

  Run standard testing:

  1. DFCI_InitialState
  2. DFCI_InTuneEnroll
  3. DFCI_InTuneRollCerts
  4. DFCI_InTunePermissions
  5. DFCI_InTuneSettings
  6. DFCI_InTuneBadUpdate
  7. DFCI_InTuneUnenroll

  Integration Instructions

  N/A

    </blockquote>
    <hr>
  </details>
  

Full Changelog: v2.3.0...v2.3.1