Bug 1814045 - Fixes for Flatpak OCI authenticator
Summary: Fixes for Flatpak OCI authenticator
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: flatpak
Version: 8.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.2
Assignee: David King
QA Contact: Desktop QE
Depends On:
TreeView+ depends on / blocked
Reported: 2020-03-16 20:56 UTC by Owen Taylor
Modified: 2020-04-28 16:10 UTC (History)
5 users (show)

Fixed In Version: flatpak-1.6.2-2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-04-28 16:10:45 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:1767 0 None None None 2020-04-28 16:10:50 UTC

Description Owen Taylor 2020-03-16 20:56:52 UTC
Testing of Flatpak-1.6 against the internal container registry, registry.redhat.io, and registry.redhat.com revealed some defects that it would be good to fix for 8.2.

 * flatpak cannot authenticate to the internal container registry, blocking testing of whether installing the Flatpaks we will ship in 8.2 from a registry works correctly:


 * downloading registry.redhat.io after prompting the user for username/password is twice as slow as it needs to be:


Comment 2 Owen Taylor 2020-03-16 21:03:10 UTC
Switched from blocker to exception, since harm is is fairly modest:
 - installing Flatpaks from container registries would be less responsive and possibly look buggy
 - pre-release testing would be harder.

Risks of these fixes should, however, also be small - they are small self-contained patches that only affect the installing-from-OCI registries code paths.

Comment 8 errata-xmlrpc 2020-04-28 16:10:45 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.