From: Paul Barker <paul@pbarker.dev>
To: alex.kanavin@gmail.com, geissonator@gmail.com
Cc: openembedded-core@lists.openembedded.org,
Andrew Geissler <geissonator@yahoo.com>
Subject: Re: [OE-core] [PATCH] global: convert all http to https
Date: Mon, 19 Jan 2026 12:41:29 +0000 [thread overview]
Message-ID: <95b21b1f4a91a3d74faedaf62932a66d7ee26497.camel@pbarker.dev> (raw)
In-Reply-To: <CANNYZj896UuNjPEzb4yOdQHe6dX=2oAxZGf6bF1Av2cGShLpNw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1787 bytes --]
On Mon, 2026-01-19 at 13:29 +0100, Alexander Kanavin via
lists.openembedded.org wrote:
> I don't necessarily disagree with the conversion, but I would like
> proper verification of all links, and not not just 'some random
> validation'. You can extract all the new links from the patch and
> write a script that runs wget on them perhaps.
>
> I also want to point out that there's no mechanism to enforce
> https-only layer metadata. New http links will creep in, there's no
> test to stop them.
>
> Alex
>
> On Fri, 16 Jan 2026 at 20:13, Andrew Geissler via
> lists.openembedded.org <geissonator=gmail.com@lists.openembedded.org>
> wrote:
> >
> > Recently an internal lab network turned off all outgoing http access.
> > This means we are unable to build oe-core without manually setting up a
> > local cache or mirror. Given the security vulnerabilities around http and
> > that moving to https appears to have no impact on building, this commit
> > just moves everything over to https.
> >
> > I wrote a python script and had it leave the following http links as-is:
> > - http://localhost, http://127.0.0.1
> > - http://example.com
> > - http://errors.yoctoproject.org
> >
> > For testing I confirmed core-image-minimal still builds and did some
> > random validation of the links changed (but not every one of them).
Further to what Alex said: This patch needs splitting up to make it
reviewable. Perhaps one patch changing links in comments, one patch
changing links in HOMEPAGE/BUGTRACKER variables, and one patch changing
SRC_URI entries.
Links such as http://www.opensource.org/licenses/mit-license.php should
be replaced with a pointer to the LICENSE.MIT file at the root of the
repository.
Best regards,
--
Paul Barker
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2026-01-19 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 19:12 [PATCH] global: convert all http to https Andrew Geissler
2026-01-19 12:29 ` [OE-core] " Alexander Kanavin
2026-01-19 12:41 ` Paul Barker [this message]
2026-01-22 17:57 ` Andrew Geissler
2026-01-22 18:00 ` [PATCH] global: convert all SRC_URI " Andrew Geissler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=95b21b1f4a91a3d74faedaf62932a66d7ee26497.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=alex.kanavin@gmail.com \
--cc=geissonator@gmail.com \
--cc=geissonator@yahoo.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox