Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFE: Support for requesting metalink via header on baseurl #251

Open
Conan-Kudo opened this issue Jul 8, 2021 · 3 comments
Open

RFE: Support for requesting metalink via header on baseurl #251

Conan-Kudo opened this issue Jul 8, 2021 · 3 comments

Comments

@Conan-Kudo
Copy link
Member

Conan-Kudo commented Jul 8, 2021

openSUSE's mirror infrastructure is set up so that the download redirector will return metalink information upon request for each file when "Accept: */*, application/metalink+xml, application/metalink4+xml" is passed in as a header.

This is used by libzypp to be able to selectively metadata from the primary server and fetch packages from mirrors with failover. We should have support for this too.

This means, for example: https://download.opensuse.org/tumbleweed/repo/oss/ will have metadata fetched from the redirector and then everything else will be fetched from mirrors.

Having support for this would also allow us to add similar capabilities to Fedora MirrorManager.

@DemiMarie
Copy link

If I turn off metalinks (by using baseurl), I expect none of the metalink code to run. The reason I would turn off metalinks is the reduced attack surface.

@Conan-Kudo
Copy link
Member Author

Conan-Kudo commented Jan 21, 2022

Yes, but the idea with this feature is that the repomd.xml and repomd.xml.asc files can be fetched from the master server, and all the RPMs can be fetched via metalink. That can be very useful from a security perspective without punishing a server's allotted bandwidth.

@DemiMarie
Copy link

Yes, but the idea with this feature is that the repomd.xml and repomd.xml.asc files can be fetched from the master server, and all the RPMs can be fetched via metalink. That can be very useful from a security perspective without punishing a server's allotted bandwidth.

That is an improvement over using metalinks for everything, yes, but I would prefer if the metalinks were statically-generated and signed. This might require a Debian-style CDN, though. I am specifically worried about libxml2, which is a rather large C library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants