Skip to content

Releases: microsoft/mu_oem_sample

v2024050000.0.0

28 Aug 15:12
@apop5 apop5
v2024050000.0.0
6959ebb
Compare
Choose a tag to compare
v2024050000.0.0 Latest
Latest

Initial Release notes of 202405 contain a full list of mu changes on top of edk2-stable202405

PR associated with the commit can be found at the bottom of the information pane reached by clicking on the commit hash
image

What's Changed## 🚀 Features & ✨ Enhancements

  • Enable CodeQL as part of PR process. Add codeql filters file for codeql issuse that should be ignored.
    Change Details
      6959ebb
  • Repo File Sync: 202405 Branch Transition Updates. (#233)
    Change Details
      d3ac723
  • pip: update edk2-pytool-extensions requirement from ~=0.27.10 to ~=0.27.11 (#232)
    Change Details
      fc94172
  • Repo File Sync: synced file(s) with microsoft/mu_devops (#231)
    Change Details
      4d54415
  • pip: update edk2-pytool-library requirement from ~=0.21.9 to ~=0.21.10 (#229)
    Change Details
      2cea6be
  • pip: bump antlr4-python3-runtime from 4.13.1 to 4.13.2 (#230)
    Change Details
      e725bfc
  • pip: update edk2-pytool-library requirement from ~=0.21.8 to ~=0.21.9 (#228)
    Change Details
      eef3b59
  • pip: bump regex from 2024.5.15 to 2024.7.24 (#227)
    Change Details
      b495936
  • pip: update edk2-pytool-extensions requirement from ~=0.27.9 to ~=0.27.10 (#226)
    Change Details
      d771c43
  • pip: update edk2-pytool-extensions requirement from ~=0.27.6 to ~=0.27.9 (#225)
    Change Details
      2435689
  • GitHub Action: Bump robinraju/release-downloader from 1.10 to 1.11 (#223)
    Change Details
      2181835
  • Repo File Sync: synced file(s) with microsoft/mu_devops (#222)
    Change Details
      3293d5c
  • pip: update edk2-pytool-library requirement from ~=0.21.7 to ~=0.21.8 (#221)
    Change Details
      4e98aef
  • pip: update edk2-pytool-extensions requirement from ~=0.27.5 to ~=0.27.6 (#220)
    Change Details
      a498d76
  • pip: update edk2-pytool-library requirement from ~=0.21.6 to ~=0.21.7 (#219)
    Change Details
      ec47a4c
  • pip: update edk2-pytool-library requirement from ~=0.21.5 to ~=0.21.6 (#218)
    Change Details
      45e5f04
  • pip: update edk2-pytool-extensions requirement from ~=0.27.4 to ~=0.27.5 (#217)
    Change Details
      aa511d5
  • Repo File Sync: synced file(s) with microsoft/mu_devops (#216)
    Change Details
      d76cd65
  • pip: bump regex from 2024.5.10 to 2024.5.15 (#215)
    Change Details
      200eda9
  • pip: bump pygount from 1.6.1 to 1.8.0 (#214)
    Change Details
      00e8b6a
  • pip: bump regex from 2024.4.28 to 2024.5.10 (#213)
    Change Details
      0f008be
  • Repo File Sync: .gitattributes: Prevent line ending conversion (#212)
    Change Details
      f23fa34
Assets 2
Loading

v2023110000.0.2

14 May 00:32
@github-actions github-actions
v2023110000.0.2
6cd87ea
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v2023110000.0.2

What's Changed

🔐 Security Impacting

  • OemPkg: DfciDeviceIdSupportLib: Fixing uninitialized variable being used @kuqin12 (#211)
    Change Details
      # Preface

    Please ensure you have read the contribution docs prior
    to submitting the pull request. In particular,
    pull request guidelines.

    Description

    There are a few instances where the variables could be used without being initialized in DfciDeviceIdSupportLib. This change is made to fix such cases.

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

    • 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

    Tested on QEMU Q35 and booted to UEFI shell.

    Integration Instructions

    N/A

      </blockquote>
  <hr>
</details>

Full Changelog: v2023110000.0.1...v2023110000.0.2

Contributors

kuqin12
Assets 2
Loading

v2023110000.0.1

05 Mar 15:26
@github-actions github-actions
v2023110000.0.1
2d1aa5c
Compare
Choose a tag to compare
v2023110000.0.1

What's Changed

  • [CHERRY-PICK] Add StackCheckLib Instances to Platform DSC Files (#198) @TaylorBeebe (#199)
    Change Details
      ## Description

    An instance of StackCheckLib must be in each DSC to accommodate -fstack-protector and /GS flags.

    • 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

    Tested in pipelines

    Integration Instructions

    N/A



  • remove edk2-basetools @Javagedes (#193)
    Change Details
      ## Description

    Removes edk2-basetools from pip-requirements.txt and any usage of it in the CISettings.py. The is done as there are changes in the build tools python source code that are available locally in BaseTools (as it is managed by Project Mu) that is not available in edk2-basetools.

    • 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

    Verified the build system continues to use the local python source

    Integration Instructions

    N/A - only effects this repository's CI system.



Full Changelog: v2023110000.0.0...v2023110000.0.1

Contributors

Javagedes and TaylorBeebe
Assets 2
Loading

v2023020000.0.8

27 Aug 19:58
@github-actions github-actions
v2023020000.0.8
ad2f68c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v2023020000.0.8

What's Changed

  • Add StackCheckLib Instances to Platform DSC Files @TaylorBeebe (#198)
    Change Details
      ## Description

    An instance of StackCheckLib must be in each DSC to accommodate -fstack-protector and /GS flags.

    • 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

    Tested in pipelines

    Integration Instructions

    N/A

      </blockquote>
  <hr>
</details>

Full Changelog: v2023020000.0.7...v2023020000.0.8

Contributors

TaylorBeebe
Assets 2
Loading

v2023110000.0.0

05 Feb 15:16
@github-actions github-actions
v2023110000.0.0
f29260e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v2023110000.0.0

What's Changed

First 202311 Mu OEM Sample release 🎉.

  • [Rebase \& FF] [Cherry-pick] Get all the missing commits from 202302 into 202311 @kenlautner (#186)
    Change Details
      ## Description

    Cherry-pick the commits from 202302 that are missing from 202311 since the creation of the release branch.

    • 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

    CI

    Integration Instructions

    N/A



  • Updated CISettings.py to use the edk2toolext codeql helpers @kenlautner (#178)
    Change Details
      ## Description

    The 202311 rebase moved the codeql plugin from .pytool to Basetools. This requires a change in CISettings.py to reference the correct codeql helper functions. Instead of using the internal versions we instead move to the edk2 pytool extensions version.

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

    • 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

    Tested with CI.

    Integration Instructions

    N/A



  • OemPkg/SecureBootKeyStoreLibOem: Delete @Javagedes (#164)
    Change Details
      ## Description

    Removes SecureBootKeyStoreLibOem from OemPkg in favor of SecureBootKeyStoreLib in MsCorePkg.

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

    • 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

    Verified QemuQ35Pkg continues to build with the new version of SecurebootKeyStoreLib provided by MsCorePkg.

    Integration Instructions

    Switch from OemPkg's SecureBootKeyStoreLib implementation. Follow integration instructions provided by the package.



  • Fix Possible BootMenu Failure @TaylorBeebe (#138)
    Change Details
      ## Description BootMenu should have a DEPEX on gEdkiiFormBrowserEx2ProtocolGuid and should not return failure (to avoid unloading the driver after creating events and installing protocol interfaces).
    • 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

    Tested on Q35

    Integration Instructions

    N/A



  • Clears the DebugDirectory of the Debug information for Release builds of HelloUefi @Flickdm (#123)
    Change Details
      # Preface

    Please ensure you have read the contribution docs prior
    to submitting the pull request. In particular,
    pull request guidelines.

    Description

    This is a workaround for an issue in GenFw

    On linux when building using GCC5 in RELEASE the PE DebugDirectory includes the full path to the intermittent DLL.

    See:

    00000330: 3403 0000 4e42 3130 0000 0000 0000 0000 4...NB10........
    00000340: 0000 0000 2f68 6f6d 652f 7573 6572 2d78 ..../home/user-x
    00000350: 782f 6d75 5f6f 656d 5f73 616d 706c 652f x/mu_oem_sample/
    00000360: 4275 696c 642f 4f65 6d50 6b67 2f52 454c Build/OemPkg/REL
    00000370: 4541 5345 5f47 4343 352f 5836 342f 4f65 EASE_GCC5/X64/Oe
    00000380: 6d50 6b67 2f48 656c 6c6f 5565 6669 2f48 mPkg/HelloUefi/H
    00000390: 656c 6c6f 5565 6669 2f44 4542 5547 2f48 elloUefi/DEBUG/H
    000003a0: 656c 6c6f 5565 6669 2e64 6c6c 0000 0000 elloUefi.dll....
    000003b0: 0000 0000 0000 0000 0000 0000 0000 0000 ................

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

    • Impacts functionality?
    • Simply zeros out the timestamps and debug directory using GenFW
    • Impacts security?
    • Breaking change?
      • If anyone is actually consuming the DebugDirectory, this would be a breaking change. This is mitigated by only removing it in this application on RELEASE builds.
    • Includes tests?
    • Includes documentation?

    How This Was Tested

    Built on WSL2 Ubuntu with GCC5 tool chain

    Integration Instructions

    N/A



  • OemPkg/HelloUefi - CI fixes @Flickdm (#117)
    Change Details
      ## Description

    This is the simplest possible UEFI application, it differs from HelloWorld in that it drops dependencies on libraries, and eliminates the PCD logic, this application ideal purpose is to be used to test secur...

Read more

Contributors

spbrogan, Flickdm, and 7 other contributors
Assets 2
Loading

v2023020000.0.7

05 Feb 15:14
@github-actions github-actions
v2023020000.0.7
d6480bc
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v2023020000.0.7

What's Changed

  • Update pip-requirements.txt @Javagedes (#183)
    Change Details
      ## Description

    Updates edk2-pytool-extensions and edk2-pytool-library to work with the latest commit of MU_BASECORE

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

    • 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

    N/A

    Integration Instructions

    N/A



  • .git-blame-ignore-revs: Ignore Line Ending and Uncrustify only commits @makubacki (#175)
    Change Details
      ## Description

    Adds commits that only applied Uncrustify formatting or converted
    line endings to a .git-blame-ignore-revs file so they are ignored
    by git blame. This is supported by GitHub:
    https://github.blog/changelog/2022-03-24-ignore-commits-in-the-blame-view-beta/

    This helps clean up git blame by filtering out these changes.

    Note: This file needs to be updated on rebase branches. Processes
    like filter-branch can automatically update relevant SHAs.

    • 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

    • git blame

    Integration Instructions

    N/A



  • OemPkg/SecureBootKeyStoreLibOem: Delete @Javagedes (#164)
    Change Details
      ## Description

    Removes SecureBootKeyStoreLibOem from OemPkg in favor of SecureBootKeyStoreLib in MsCorePkg.

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

    • 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

    Verified QemuQ35Pkg continues to build with the new version of SecurebootKeyStoreLib provided by MsCorePkg.

    Integration Instructions

    Switch from OemPkg's SecureBootKeyStoreLib implementation. Follow integration instructions provided by the package.



🔐 Security Impacting

  • Use New Stack Cookie Library @TaylorBeebe (#160)
    Change Details
      ## Description

    MdePkg/MdeLibs.dsc.inc contains the definitions for the new stack cookie libraries.

    • 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

    Tested on Q35 GCC and MSVC builds

    Integration Instructions

    N/A



Full Changelog: v2023020000.0.6...v2023020000.0.7

Contributors

makubacki, Javagedes, and TaylorBeebe
Assets 2
Loading

v2023020000.0.6

22 Sep 23:43
@github-actions github-actions
v2023020000.0.6
eb29073
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v2023020000.0.6

What's Changed

  • Fix Possible BootMenu Failure @TaylorBeebe (#138)
    Change Details
      ## Description BootMenu should have a DEPEX on gEdkiiFormBrowserEx2ProtocolGuid and should not return failure (to avoid unloading the driver after creating events and installing protocol interfaces).
    • 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

    Tested on Q35

    Integration Instructions

    N/A



Full Changelog: v2023020000.0.5...v2023020000.0.6

Contributors

TaylorBeebe
Assets 4
Loading

v2023020000.0.5

28 Jul 15:01
@github-actions github-actions
v2023020000.0.5
a92ee03
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v2023020000.0.5

What's Changed

  • Clears the DebugDirectory of the Debug information for Release builds of HelloUefi @Flickdm (#123)
    Change Details
      # Preface

    Please ensure you have read the contribution docs prior
    to submitting the pull request. In particular,
    pull request guidelines.

    Description

    This is a workaround for an issue in GenFw

    On linux when building using GCC5 in RELEASE the PE DebugDirectory includes the full path to the intermittent DLL.

    See:

    00000330: 3403 0000 4e42 3130 0000 0000 0000 0000 4...NB10........
    00000340: 0000 0000 2f68 6f6d 652f 7573 6572 2d78 ..../home/user-x
    00000350: 782f 6d75 5f6f 656d 5f73 616d 706c 652f x/mu_oem_sample/
    00000360: 4275 696c 642f 4f65 6d50 6b67 2f52 454c Build/OemPkg/REL
    00000370: 4541 5345 5f47 4343 352f 5836 342f 4f65 EASE_GCC5/X64/Oe
    00000380: 6d50 6b67 2f48 656c 6c6f 5565 6669 2f48 mPkg/HelloUefi/H
    00000390: 656c 6c6f 5565 6669 2f44 4542 5547 2f48 elloUefi/DEBUG/H
    000003a0: 656c 6c6f 5565 6669 2e64 6c6c 0000 0000 elloUefi.dll....
    000003b0: 0000 0000 0000 0000 0000 0000 0000 0000 ................

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

    • Impacts functionality?
    • Simply zeros out the timestamps and debug directory using GenFW
    • Impacts security?
    • Breaking change?
      • If anyone is actually consuming the DebugDirectory, this would be a breaking change. This is mitigated by only removing it in this application on RELEASE builds.
    • Includes tests?
    • Includes documentation?

    How This Was Tested

    Built on WSL2 Ubuntu with GCC5 tool chain

    Integration Instructions

    N/A



Full Changelog: v2023020000.0.4...v2023020000.0.5

Contributors

Flickdm
Assets 4
Loading

v2023020000.0.4

14 Jul 17:27
@github-actions github-actions
v2023020000.0.4
746b442
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v2023020000.0.4

What's Changed

  • OemPkg/HelloUefi - CI fixes @Flickdm (#117)
    Change Details
      ## Description

    This is the simplest possible UEFI application, it differs from HelloWorld in that it drops dependencies on libraries, and eliminates the PCD logic, this application ideal purpose is to be used to test secure boot certificates as it's attack surface is minimal.

    • Impacts functionality?
    • Impacts security?
    • Breaking change?
    • Includes tests?
    • Includes documentation?

    How This Was Tested

    Built with stuart_ci_build and wsl

    Integration Instructions

    N/A



  • Add simple UEFI application - HelloUefi @Flickdm (#116)
    Change Details
      ## Description

    This is the simplest possible UEFI application. It differs from 'HelloWorld' by dropping PCD logic and dependencies

    • Impacts functionality?

    • Impacts security?

    • Breaking change?

    • Includes tests?

    • Includes documentation?

    How This Was Tested

    Ran on QemuQ35

    Integration Instructions

    N/A

      </blockquote>
  <hr>
</details>

🐛 Bug Fixes

  • OemPkg: Fix build @makubacki (#121)
    Change Details
      ## Description

    Fix errors in several CI plugins to pass CI.

    • 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

    CI build.

    Integration Instructions

    N/A



🔐 Security Impacting

  • adding stack cookie support @Flickdm (#119)
    Change Details
      # Preface

    Please ensure you have read the contribution docs prior
    to submitting the pull request. In particular,
    pull request guidelines.

    Description

    Issue 118

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

    • Impacts functionality?
      • Yes, builds with stack cookies by default for OemPkg when using stuart_ci_build
    • Impacts security?
      • Yes, adds stack cookies
    • Breaking change?
      • This shouldn't be breaking
    • Includes tests?
      • No
    • Includes documentation?
      • No

    How This Was Tested

    This was built in a windows environment with VS2022 using stuart_ci_build and built on a linux environment using WSL2 on ubuntu 22.04.2 using GCC5

    Integration Instructions

    N/A



📖 Documentation Updates

  • HelloUefi: Add 30 second stall @Flickdm (#120)
    Change Details
      ## Description

    This application is the simplest UEFI application possible, with no dependencies. These changes add a 30 second stall such that a platform may boot directly to this application and see "Hello UEFI!" with no need for a shell to run it (Such as ShellPkg).

    • Impacts functionality?
    • Impacts security?
    • Breaking change?
    • Includes tests?
    • Includes documentation?
      • Readme.md

    How This Was Tested

    Ran on a physical machine, QemuQ35,

    built With GCC and VS2022

    Integration Instructions

    N/A

      </blockquote>
  <hr>
</details>

Full Changelog: v2023020000.0.3...v2023020000.0.4

Contributors

Flickdm and makubacki
Assets 2
Loading

v2023020000.0.3

28 Jun 14:05
@github-actions github-actions
v2023020000.0.3
6474d1a
Compare
Choose a tag to compare
v2023020000.0.3

What's Changed

  • ci.yaml: add PrEval entry @Javagedes (#111)
    Change Details
      ## Description

    Add a PrEval entry to all ci.yaml files to enable the new PrEval Policy 5.

    • 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

    N/A

    Integration Instructions

    N/A



  • Fixing Uncrustify break @kuqin12 (#112)
    Change Details
      # Preface

    Please ensure you have read the contribution docs prior
    to submitting the pull request. In particular,
    pull request guidelines.

    Description

    This change fixed an Uncrustify failure on the latest top of mainline branch.

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

    • 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

    Uncrustify fix, no functional change.

    Integration Instructions

    N/A

      </blockquote>
  <hr>
</details>
  • Display the Type 1 serial number instead of the Type 3 serial number @mikeytdisco (#104)
    Change Details
      ## Description

    The sample Front Page is displaying the Type 3 serial number and should display the Type 1 serial number.

    This one fixes #102

    • 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

    Tested in QemuQ35Pkg

    Integration Instructions

    N/A

      </blockquote>
  <hr>
</details>

Full Changelog: v2023020000.0.2...v2023020000.0.3

Contributors

mikeytdisco, Javagedes, and kuqin12
Assets 2
Loading