From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Devoogdt <thomas@devoogdt.com>
Cc: buildroot@buildroot.org, Thomas Perale <thomas.perale@mind.be>,
Thomas Devoogdt <thomas.devoogdt@barco.com>
Subject: Re: [Buildroot] [PATCH] utils/generate-cyclonedx: add support for certifi ssl context
Date: Thu, 13 Mar 2025 10:41:16 +0100 [thread overview]
Message-ID: <87plil6zer.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20250305085617.911367-1-thomas.devoogdt@barco.com> (Thomas Devoogdt's message of "Wed, 5 Mar 2025 09:56:17 +0100")
>>>>> "Thomas" == Thomas Devoogdt <thomas@devoogdt.com> writes:
> urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED]
> certificate verify failed: unable to get local issuer certificate
> (_ssl.c:1000)>
> Allow to fix this by e.g. using `make host-python-certifi`.
> Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
Is this on a very old machine / python setup? Are you using your host
machine's python or building host-python3?
It is not like we are doing anything special here, perhaps your ssl
configuration is outdated? Can you access the URL with curl / wget?
curl -v https://raw.githubusercontent.com/CycloneDX/specification/
..
* Server certificate:
* subject: CN=*.github.io
* start date: Mar 7 00:00:00 2025 GMT
* expire date: Mar 7 23:59:59 2026 GMT
* subjectAltName: host "raw.githubusercontent.com" matched cert's "*.githubusercontent.com"
* issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
* SSL certificate verify ok.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-03-13 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 8:56 [Buildroot] [PATCH] utils/generate-cyclonedx: add support for certifi ssl context Thomas Devoogdt
2025-03-13 9:41 ` Peter Korsgaard [this message]
2025-03-13 10:01 ` Thomas Devoogdt
2025-03-13 11:03 ` Peter Korsgaard
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=87plil6zer.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=thomas.devoogdt@barco.com \
--cc=thomas.perale@mind.be \
--cc=thomas@devoogdt.com \
/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