| commit | 8fa99b87bc6420d0cd2884ce7ced03c623d7d4ad | [log] [tgz] |
|---|---|---|
| author | Salud Lemus <saludlemus@google.com> | Mon Aug 27 22:58:41 2018 |
| committer | chrome-bot <chrome-bot@chromium.org> | Tue Sep 11 00:17:39 2018 |
| tree | 959e0107eb8db6ff6308e6da59b430e870d80635 | |
| parent | de06e79b0296adc38d51a3c920de90c115a63c1d [diff] |
UPSTREAM: fu-engine: Don't fail get-details if compiled without GPG/PKCS7 Similar to commit 7d35278 regarding the install option with a daemon compiled without GPG, but now, if you also have a daemon compiled without GPG, and if you have downloaded a CAB file from LVFS and ran get-details, it would fail to display the contents of the associated CAB file. This allows it to still display the contents of the CAB file, and a warning will be displayed in the logs. BUG=chromium:857263 TEST=fwupdmgr get-details <cab file> does not show "Not compiled with GPG support" and running "/usr/libexec/fwupd/fwupd -v" for the get-details option shows that the verification step is ignored for the CAB file (cherry-picked from commit 980f2d95519a163fe49797259e94e2b29a3c341d https://github.com/hughsie/fwupd.git master) Signed-off-by: Salud Lemus <saludlemus@google.com> Change-Id: I2ce3d4da96a3a48ed3e9a38477ca6270b3537a22 Reviewed-on: https://chromium-review.googlesource.com/1191929 Commit-Ready: Todd Broch <tbroch@chromium.org> Tested-by: Salud Lemus <saludlemus@google.com> Reviewed-by: Benson Leung <bleung@chromium.org> Reviewed-by: Todd Broch <tbroch@chromium.org>
This project aims to make updating firmware on Linux automatic, safe and reliable.
Additional information is available at the website: https://fwupd.org
The most up to date compilation instructions are available in the Wiki
This project is configured by default to download firmware from the Linux Vendor Firmware Service (LVFS).
This service is available to all OEMs and firmware creators who would like to make their firmware available to Linux users.
You can find more information about the technical details of creating a firmware capsule in the hardware vendors section of the fwupd website.
If you have a device with firmware supported by fwupd, this is how you will check for updates and apply them using fwupd's command line tools.
# fwupdmgr get-devices
This will display all devices detected by fwupd.
# fwupdmgr refresh
This will download the latest metadata from LVFS.
# fwupdmgr get-updates
If updates are available for any devices on the system, they'll be displayed.
# fwupdmgr update
This will download and apply all updates for your system.
You can find more information about the update workflow in the end users section of the fwupd website.
fwupd will encourage users to report both successful and failed updates back to LVFS. This is an optional feature, but encouraged as it provides valuable feedback to LVFS administrators and OEM developers regarding firmware update process efficacy.
The privacy policy regarding this data can be viewed on the fwupd website.
To report the status of an update run:
# fwupdmgr report-history
To clear the local history of updates:
# fwupdmgr clear-history
Only updates that were distributed from the LVFS will be reported to the LVFS.
Currently GNOME Software is the only graphical frontend available. When compiled with firmware support, it will check for updates periodically and automatically download firmware in the background.
After the firmware has been downloaded a popup will be displayed in Gnome Software to perform the update.
On Dell IoT gateways, Wyse Cloud Client Manager (CCM) has been built with fwupd support. The remote administration interface can be used to download and deploy firmware updates.