Commit Graph

4 Commits

Author SHA1 Message Date
Simon McVittie
b730771bd7 subprojects: Update bubblewrap to v0.11.0
<https://github.com/containers/bubblewrap/releases/tag/v0.11.0>

We don't use any of the new features yet, so the minimum required
version in the build system is still 0.10.0.

Signed-off-by: Simon McVittie <smcv@collabora.com>
2024-10-31 10:03:52 -05:00
Simon McVittie
417f3ca47c build: Require bubblewrap 0.10.0
This is functionally equivalent to the release candidate.

Signed-off-by: Simon McVittie <smcv@collabora.com>
2024-08-14 09:59:19 +01:00
Simon McVittie
bb8759ea10 build: Bump required bubblewrap version to 0.9.901 (0.10.0 rc1)
We need this for the --bind-fd option, which will close a race
condition in our solution to CVE-2024-42472.

Signed-off-by: Simon McVittie <smcv@collabora.com>
2024-08-12 19:33:29 +01:00
Simon McVittie
c982e591ba Use Meson wrap files for bubblewrap and xdg-dbus-proxy
When combined with using `git subtree` for our mandatory vendored
dependencies, this avoids differences between what we ship in our git
repository (available to users via `git clone` or by unpacking the
result of `git archive`), and what's in our official source code
releases (which are the result of `meson dist`).

Differences between those artifacts would provide an attractive place
for attackers to hide malware, for example in CVE-2024-3094, so
avoiding differences is a good "nothing up my sleeve" mechanism to
make it less appealing for attackers to target Flatpak.

With default Meson settings, the wrap files will be used automatically
to download our suggested versions of these dependencies, unless
the `-Dsystem_bubblewrap=...`, `-Dsystem_dbus_proxy=...` Meson options
are used. In environments where automatic downloads are disabled via
`-Dwrap_mode=nodownload`, for example many Linux distributions,
specifying a system copy becomes mandatory.

Signed-off-by: Simon McVittie <smcv@collabora.com>
2024-05-06 17:11:23 +01:00