Please stop build-depending on libgnome-keyring
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| chromium-browser (Ubuntu) |
Medium
|
Olivier Tilloy | ||
| Xenial |
Medium
|
Olivier Tilloy | ||
| Bionic |
Medium
|
Olivier Tilloy | ||
| Disco |
Medium
|
Olivier Tilloy |
Bug Description
libgnome-keyring is not maintained anymore, but chromium build-depends on it. It should be using libsecret instead. The generated binaries depend on neither library, which is a bit confusing.
Julian Andres Klode (juliank) wrote : | #1 |
Julian Andres Klode (juliank) wrote : | #2 |
As a side note, Debian also builds with use_gnome_keyring = false, so it's perfectly safe to do so.
Olivier Tilloy (osomon) wrote : | #3 |
chromium doesn't expose a build flag to use the system-wide libsecret, it always relies on the vendorized library.
Changed in chromium-browser (Ubuntu): | |
assignee: | nobody → Olivier Tilloy (osomon) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in chromium-browser (Ubuntu): | |
status: | In Progress → Fix Committed |
Launchpad Janitor (janitor) wrote : | #4 |
This bug was fixed in the package chromium-browser - 74.0.3729.
---------------
chromium-browser (74.0.3729.
* debian/control: remove libgnome-
* debian/rules: build with use_gnome_
* debian/
-- Olivier Tilloy <email address hidden> Wed, 08 May 2019 12:15:30 +0200
Changed in chromium-browser (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in chromium-browser (Ubuntu Xenial): | |
assignee: | nobody → Olivier Tilloy (osomon) |
Changed in chromium-browser (Ubuntu Bionic): | |
assignee: | nobody → Olivier Tilloy (osomon) |
Changed in chromium-browser (Ubuntu Disco): | |
assignee: | nobody → Olivier Tilloy (osomon) |
Changed in chromium-browser (Ubuntu Xenial): | |
importance: | Undecided → Medium |
Changed in chromium-browser (Ubuntu Bionic): | |
importance: | Undecided → Medium |
Changed in chromium-browser (Ubuntu Disco): | |
importance: | Undecided → Medium |
Changed in chromium-browser (Ubuntu Xenial): | |
status: | New → Triaged |
Changed in chromium-browser (Ubuntu Bionic): | |
status: | New → Triaged |
Changed in chromium-browser (Ubuntu Disco): | |
status: | New → Triaged |
Changed in chromium-browser (Ubuntu Xenial): | |
status: | Triaged → In Progress |
Changed in chromium-browser (Ubuntu Bionic): | |
status: | Triaged → In Progress |
Changed in chromium-browser (Ubuntu Disco): | |
status: | Triaged → In Progress |
Olivier Tilloy (osomon) wrote : | #5 |
Launchpad Janitor (janitor) wrote : | #6 |
This bug was fixed in the package chromium-browser - 79.0.3945.
---------------
chromium-browser (79.0.3945.
* Upstream release: 79.0.3945.130
- CVE-2020-6378: Use-after-free in speech recognizer.
- CVE-2020-6379: Use-after-free in speech recognizer.
- CVE-2020-6380: Extension message verification error.
* debian/control: remove libgnome-
* debian/rules: build with use_gnome_
* debian/
-- Olivier Tilloy <email address hidden> Mon, 27 Jan 2020 17:57:12 +0100
Changed in chromium-browser (Ubuntu Bionic): | |
status: | In Progress → Fix Released |
Launchpad Janitor (janitor) wrote : | #7 |
This bug was fixed in the package chromium-browser - 79.0.3945.
---------------
chromium-browser (79.0.3945.
* Upstream release: 79.0.3945.130
- CVE-2020-6378: Use-after-free in speech recognizer.
- CVE-2020-6379: Use-after-free in speech recognizer.
- CVE-2020-6380: Extension message verification error.
* debian/control: remove libgnome-
* debian/rules: build with use_gnome_
* debian/
-- Olivier Tilloy <email address hidden> Mon, 27 Jan 2020 17:44:47 +0100
Changed in chromium-browser (Ubuntu Xenial): | |
status: | In Progress → Fix Released |
Changed in chromium-browser (Ubuntu Disco): | |
status: | In Progress → Fix Committed |
Changed in chromium-browser (Ubuntu Disco): | |
status: | Fix Committed → Won't Fix |
FWIW, it seems libsecret is shipped as a vendorized library, as the build log says:
[7656/36567] AR obj/third_ party/libsecret /libsecret. a
Might be useful to use the system-wide libsecret instead.