-
Notifications
You must be signed in to change notification settings - Fork 30
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]: Prevent user loading wrong config xml file in ConfigEditor #418
Comments
@kanechen66 , this is a good idea, thank you for implementing. |
Since the BIOS SHA is the git commit id, and not all BIOS will implement it in SMBIOS, and it is possible that multiple BIOS are using the same XML content, which should still be allowed, so I have different thought about how to check it.
|
Hi all,
I propose using all the elements (including tag) in xml to hash and BIOS save this hash to a variable. let me know if it's ok, if it's ok, i will implement in this way. |
I created a PR here #421 |
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. |
all changes are landed. close it |
Feature Overview
In the current ConfigEditor design, there is no version check for xml.
It may lead to problems such as user loading wrong xml file so that the config is not taken effect or is not shown properly on UI.
Solution Overview
We have a proposal to add BIOS version and sha information in the xml file
ex:
Then the configeditor can read BIOS sha from smbios type 11 oemstring and bios version from smbios type 0
it can provide a hint that user is using the wrong xml and unexpected behavior issues could happen.
Feel free to provide your thoughts on this :)
Alternatives Considered
No response
Urgency
Low
Are you going to implement the feature request?
I will implement the feature
Do you need maintainer feedback?
Maintainer feedback requested
Anything else?
No response
The text was updated successfully, but these errors were encountered: