Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
artgup opened this issue Nov 28, 2023 · 3 comments
Closed
Labels
state:backlog In the backlog state:needs-owner Needs an issue owner to be assigned state:needs-triage Needs to triaged to determine next steps type:feature-request A new feature proposal urgency:medium Important with a moderate impact

Comments

@artgup
Copy link

artgup commented Nov 28, 2023

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

@artgup artgup added state:needs-triage Needs to triaged to determine next steps type:feature-request A new feature proposal labels Nov 28, 2023
@github-actions github-actions bot added urgency:medium Important with a moderate impact state:needs-owner Needs an issue owner to be assigned labels Nov 28, 2023
Copy link

This issue has been automatically marked as stale because it has not had activity in 45 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@github-actions github-actions bot added the state:stale Has not been updated in a long time label Jan 12, 2024
@makubacki makubacki removed the state:stale Has not been updated in a long time label Jan 17, 2024
Copy link

github-actions bot commented Mar 2, 2024

This issue has been automatically marked as stale because it has not had activity in 45 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@github-actions github-actions bot added the state:stale Has not been updated in a long time label Mar 2, 2024
Copy link

github-actions bot commented Mar 9, 2024

This issue has been automatically been closed because it did not have any activity in 45 days and no follow up within 7 days after being marked stale. Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 9, 2024
@makubacki makubacki added state:backlog In the backlog and removed state:stale Has not been updated in a long time labels Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:backlog In the backlog state:needs-owner Needs an issue owner to be assigned state:needs-triage Needs to triaged to determine next steps type:feature-request A new feature proposal urgency:medium Important with a moderate impact
Projects
None yet
Development

No branches or pull requests

2 participants