![]() Using old versions of gcab we could only do one thing: extract the files in the cabinet archive to a new directory in /tmp, and then fwupd would have to read them back in to memory to parse them. This was both inelegant and wasteful, and probably not an awesome idea from a security or privacy point of view. Using libgcab >= 1.0 we can decompress to a GBytes blob, and then verify the firmware and metainfo file without anything being written to disk. As this is a security sensitive operation, move the fwupd-specific helper code out of libappstream-glib and also add a lot of internal self tests. The gcab code will have to remain in libappstream-glib for a long time, but we don't have to use it. Handling the cab file here also allows us to fix two long-standing bugs: * MetaInfo or firmware files in a subdirectory are handled correctly * The archive can also be self-signed using PKCS7 instead of using GPG |
||
---|---|---|
.github | ||
.tx | ||
contrib | ||
data | ||
docs | ||
libfwupd | ||
plugins | ||
po | ||
policy | ||
src | ||
.gitignore | ||
.travis.yml | ||
AUTHORS | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
COPYING | ||
MAINTAINERS | ||
meson_options.txt | ||
meson_post_install.sh | ||
meson.build | ||
NEWS | ||
README.md | ||
RELEASE |
fwupd
This project aims to make updating firmware on Linux automatic, safe and reliable.
Additional information is available at the website: https://fwupd.org
Compiling
The most up to date compilation instructions are available in the Wiki
LVFS
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.
Basic usage flow (command line)
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.
- Updates that can be applied live (Online updates) will be done immediately.
- Updates that require a reboot (Offline updates) will be staged for the next reboot.
You can find more information about the update workflow in the end users section of the fwupd website.
Other frontends
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.