RE: [bitbake-devel] [PATCH] fetch2/crate: support user-defined protocols

My company has an internal registry that is served over HTTP. We can, and do, expose it also over HTTPS using a self-signed certificate, but installing said certificate in some locations (mainly CI runners) can be difficult and we don't see much of a reason when the registry is already restricted to internal traffic by firewall rules.

All that said, I believe the patch you linked would resolve this issue for us without the need for explicit HTTP support.

Thank you,
Gabriel Smith

-----Original Message-----
From: Paul Barker <[email protected]> 
Sent: Friday, June 19, 2026 8:16 AM
To: Gabriel A Smith <[email protected]>; [email protected]
Subject: Re: [bitbake-devel] [PATCH] fetch2/crate: support user-defined protocols

On Wed, 2026-06-17 at 18:59 +0000, Gabriel A Smith via lists.openembedded.org wrote:
> From cd89f0c841d9611d79047c70045a05f6ac41da56 Mon Sep 17 00:00:00 2001
> From: Gabriel Smith <[email protected]>
> Date: Wed, 17 Jun 2026 17:53:56 +0000
> Subject: [PATCH] fetch2/crate: support user-defined protocols
> 
> By default HTTPS is used for crate downloads, but both HTTP and FTP 
> are also supported by wget. FTP is not supported by crate registries 
> so it is not recommended. This adds a protocol parameter similar to 
> the git fetcher to allow a user to specify a different protocol.
> 
> Documentation has been updated to mention the new parameter.
> 
> Signed-off-by: Gabriel Smith <[email protected]>

Hi Gabriel,

What's the motivation for this patch? I don't think we should encourage use of insecure protocols.

If there's a strong reason for supporting this, please also rebase on top of the patch for configurable registry and index URLs support [1] and send a v2.

[1]: https://lore.kernel.org/bitbake-devel/[email protected]/

Thanks,

--
Paul Barker


**********************************************************************
DISCLAIMER:
Privileged and/or Confidential information may be contained in this message. If you are not the addressee of this message, you may not copy, use or deliver this message to anyone. In such event, you should destroy the message and kindly notify the sender by reply e-mail. It is understood that opinions or conclusions that do not relate to the official business of the company are neither given nor endorsed by the company. Thank You.