microsoft / mu_tiano_plus

Project Mu TianoCore Plus

Project Mu Tiano Plus Repository

Host Type & Toolchain	Build Status	Test Status	Code Coverage
Windows_VS2019
Ubuntu_GCC5

This repository is part of Project Mu. Please see Project Mu for details https://microsoft.github.io/mu

Branch Status - release/202311

Status

In Development

Entered Development

2023/12/18

Anticipated Stabilization

Feb 2024

Branch Changes - release/202311

Breaking Changes-dev

• Incomplete

Main Changes-dev

• Added RSA4096 support in SecurityPkg
• Simplified Rng algorithm selection for ARM

Bug Fixes-dev

• Incomplete

2311_RefBoot Changes

• Incomplete

2311_CIBuild Changes

• Incomplete

2311_Rebase Changes

Starting commit: 82575738fa6caeaefe188f7bb59d174f3eedf70a
Destination Commit from upstream edk2: 8736b8fdca85e02933cdb0a13309de14c9799ece

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct https://opensource.microsoft.com/codeofconduct/

For more information see the Code of Conduct FAQ https://opensource.microsoft.com/codeofconduct/faq/ or contact [email protected]. with any additional questions or comments.

Contributions

Contributions are always welcome and encouraged! Please open any issues in the Project Mu GitHub tracker and read https://microsoft.github.io/mu/How/contributing/

Copyright & License

Copyright (C) Microsoft Corporation
SPDX-License-Identifier: BSD-2-Clause-Patent

Upstream License (TianoCore)

Copyright (c) 2019, TianoCore and contributors. All rights reserved.

SPDX-License-Identifier: BSD-2-Clause-Patent

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

Subject to the terms and conditions of this license, each copyright holder and contributor hereby grants to those receiving rights under this license a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except for failure to satisfy the conditions of this license) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer this software, where such license applies only to those patent claims, already acquired or hereafter acquired, licensable by such copyright holder or contributor that are necessarily infringed by:

1. their Contribution(s) (the licensed copyrights of copyright holders and non-copyrightable additions of contributors, in source or binary form) alone; or
2. combination of their Contribution(s) with the work of authorship to which such Contribution(s) was added by such copyright holder or contributor, if, at the time the Contribution is added, such addition causes such combination to be necessarily infringed. The patent license shall not apply to any other combinations which include the Contribution.

Except as expressly stated above, no rights or licenses from any copyright holder or contributor is granted under this license, whether expressly, by implication, estoppel or otherwise.

DISCLAIMER

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

mu_tiano_plus's Issues

202208 Branch Changes section in ReadMe.rst needs to be updated

These sections need to be filled in - https://github.com/microsoft/mu_tiano_plus/blob/release/202208/ReadMe.rst:

Breaking Changes-dev
None

Main Changes-dev
None

Bug Fixes-dev
None

2202_RefBoot Changes
Incomplete

2202_CIBuild Changes
None

[Bug]: PrmInfo Doesn't Provide -r Option Advertised

Is there an existing issue for this?

• I have searched existing issues

Current Behavior

PrmInfo -? says:

However, this flag is not supported:

Expected Behavior

Either the -r flag should validate the installed PRMT ACPI table or it should not be included in the help.

Steps To Reproduce

Boot QemuQ35Pkg in mu_tiano_platforms to the EFI shell, having included PrmInfo. Run PrmInfo as shown above.

Build Environment

- OS(s): EFI Shell
- Tool Chain(s): Any
- Targets Impacted: Any

Version Information

top of tree

Urgency

Low

Are you going to fix this?

Someone else needs to fix it

Do you need maintainer feedback?

No maintainer feedback needed

Anything else?

No response

This repo is missing important files

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

[Feature]: TRNG Lib in the ARM Pkg should be optional (an opt in mechanism)

Feature Overview

The current implementation of TRNG in the ARMPkg (https://github.com/tianocore/edk2/blob/3db76e6476e493d3cda45b81bba99a645180cf35/ArmPkg/Library/ArmTrngLib/ArmTrngLib.c#L82) forces the platform to have their own implementation. There is a null version of TRNG but that has asserts in the interface implementation making it non-usable for the platform. Ideally, we want the platform to control how they want to generate their random numbers without forcing TRNG to be implemented.

Solution Overview

Ideally, we want the platform to control how they want to generate their random numbers without forcing TRNG to be implemented.

Alternatives Considered

No response

Urgency

Medium

Are you going to implement the feature request?

Someone else needs to implement the feature

Do you need maintainer feedback?

No maintainer feedback needed

Anything else?

No response