Go to file
Richard Hughes deea2da041 Use the new functionality in libgcab >= 1.0 to avoid writing temp files
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
2017-12-21 08:54:00 +00:00
.github .github: Add note how to find version before fwupd 0.9.6 2017-11-06 14:17:11 +00:00
.tx trivial: Add some files ready for a first release 2015-03-16 12:51:04 +00:00
contrib ci: mesonintrospect -> meson introspect 2017-12-13 11:08:45 -06:00
data Support AppStream metadata with relative <location> URLs 2017-12-04 15:46:54 +00:00
docs Remove autoconf-isms from the meson configure options 2017-11-27 18:07:53 +00:00
libfwupd Add more metadata to the user-agent string 2017-12-21 08:25:29 +00:00
plugins unifying: Don't duplicate a device flag from FuDevice 2017-12-14 18:12:13 +00:00
po Release fwupd 1.0.2 2017-11-28 14:31:18 +00:00
policy build: Refactor directory selection 2017-11-17 17:11:51 +00:00
src Use the new functionality in libgcab >= 1.0 to avoid writing temp files 2017-12-21 08:54:00 +00:00
.gitignore Add gitignore 2017-10-12 07:02:43 +01:00
.travis.yml contrib/debian: dynamically generate control file 2017-11-07 16:39:28 -06:00
AUTHORS Add initial build files and enough code to launch a simple D-Bus daemon 2015-02-26 18:16:40 +00:00
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 2017-09-12 15:26:14 +01:00
CONTRIBUTING.md Create CONTRIBUTING.md 2017-09-12 19:37:35 +01:00
COPYING Add initial project files 2015-02-26 13:07:00 +00:00
MAINTAINERS Add initial build files and enough code to launch a simple D-Bus daemon 2015-02-26 18:16:40 +00:00
meson_options.txt Remove autoconf-isms from the meson configure options 2017-11-27 18:07:53 +00:00
meson_post_install.sh Create /var/lib/fwupd by meson post install 2017-04-21 08:07:58 -05:00
meson.build Use the new functionality in libgcab >= 1.0 to avoid writing temp files 2017-12-21 08:54:00 +00:00
NEWS Release fwupd 1.0.2 2017-11-28 14:31:18 +00:00
README.md Remove www. from links to fwupd.org 2017-12-17 10:39:34 +00:00
RELEASE trivial: post release version bump 2017-11-28 14:59:03 +00:00

fwupd

Build Status Coverity Scan Build Status

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.