flatpak 1.0.6 release.

This release fixes an issue that lets system-wide installed applications create setuid root files inside their app dir (somewhere in /var/lib/flatpak/app). Setuid support is disabled inside flatpaks, so such files are only a risk if the user runs them manually outside flatpak.

Installing a flatpak system-wide is needs root access, so this isn't a privilege elevation for non-root users, and allowing root to install setuid files is something all traditional packaging systems allow. However flatpak tries to be better than that, in order to make it easier to trust third party repositories.

Changes in this version:

• The permissions of the files created by the apply_extra script is canonicalized and the script itself is run without any capabilities.
• Better matching of existing remotes when the local and remote configuration differs wrt collection ids.
• New flatpakrepo DeployCollectionID replaces CollectionID, doing the same thing. It is recommended to use this instead because older versions of flatpak has bugs in the support of collection ids, and this key will only be respected in versions where it works.
• The X11 socket is now mounted read-only.

flatpak 1.0.5 release.

There was a sandbox bug in the previous version where parts of the runtime /etc was not mounted read-only. In case the runtime was installed as the user (not the default) this means that the app could modify files on the runtime. Nothing in the host uses the runtime files, so this is not a direct sandbox escape, but it is possible that an app can confuse a different app that has higher permissions and so gain privileges.

Detailed changes:

• Make the /etc -> /usr/etc bind-mounts read-only.
• Make various app-specific configuration files read-only.
• flatpak is more picky about remote names to avoid problems with storing weird names in the ostree config.
• A segfault in libflatpak handling of bundles was fixed.
• Updated translations
• Fixed a regression in flatpak run that caused problems running user-installed apps when the system installation was broken.

In addition to upstream changes, this update also fixes a packaging issue and adds a missing dependency on p11-kit-server to fix accessing host TLS certificates.