-
Notifications
You must be signed in to change notification settings - Fork 0
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
Optiplex binaries parsing errors #1226
Comments
Can be replicated manually in DTS by using: wget -O "/tmp/O7010A29.exe" --user-agent='Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)' "https://dl.dell.com/FOLDER05066036M/1/O7010A29.exe"
binwalk --run-as=root -e "/tmp/O7010A29.exe" -C /tmp
uefi-firmware-parser -e "/tmp/_O7010A29.exe.extracted/65C10" -O >> log Binwalk will output warning: DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
416784 0x65C10 Zlib compressed data, default compression
WARNING: One or more files failed to extract: either no utility was found or it's unimplemented
When trying this on Fedora 41 the only difference is that binwalk manages to extract everything (
|
Fix: use current version from GitHub (not available on PyPi) https://github.com/theopolis/uefi-firmware-parser:
|
Additionaly maybe we shouldn't output stdout to |
Component
Dasharo Tools Suite
Device
Dell OptiPlex 9010
Dasharo version
v0.1.1
Dasharo Tools Suite version
v2.2.0
Test case ID
No response
Brief summary
Optiplex Dasharo Initial deployment shows binaries absence errors, but firmware installs with success.
How reproducible
100%
How to reproduce
Do initial deployment to Dasharo v0.1.1 on Optiplex 9010.
Expected behavior
Initial deployment passes without errors/warnings.
Actual behavior
Screenshots
No response
Additional context
Though, I noticed it during initial deployment on Optiplex 9010 when deploying Dasharo (Coreboot + UEFI) v0.1.1. It might as well appear on other platforms/deployment workflows.
The line that causes the issue.
Logs
Solutions you've tried
No response
The text was updated successfully, but these errors were encountered: