-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. Could not handshake: Error in the certificate verification. #424
Comments
Note #271 |
#217 suggest using 32bit, but when I use (either on a rpi, or virtual box), I still get these errors (stage-1) |
I'm not seeing this. Does it happen if you build on a Raspberry Pi without Docker? Edit: Also, aside from the issue referenced in #271, qemu is broken in other ways too unless you have one of few specific versions that work (none of which are currently distributed in any distro). |
@XECDesign every where I try I get these errors is there any guide on exactly how to do this? |
Sure, start with an armhf Raspberry Pi OS image on any pi with a large sd card (at least 32GB). I used Raspberry Pi OS lite on a 4GB pi 4. Make sure your OS is up to date:
Install the dependencies and reboot:
Checkout the repo and
Set an image name and kick off a build:
|
tried the steps you mentioned, still failing |
Not much that can be done if it's not a reproducible issue. A bit off that OP's output contains "https" paths, when pi-gen uses "http", so it shouldn't be happening without additional changes. |
Same issue here with a fresh install on a RPI4. Stage 1 fails on the first apt call because ssl certs are missing in the rootfs (I tried with both
|
If you're changing sources lists to add an https repo (which is the only way I can reproduce OP's issue), you can resolve it by pre-installing However, apt repos are secure without SSL, so it makes little sense to do so. (https://wiki.debian.org/SecureApt)
|
I've used a bare clone of this repo without any modifications. But still, at stage1 I've got:
I have no clue where those repos are coming from. Could there be mirror addresses in apt repos that are loaded dynamically? Anyway, thanks for the tips to bypass this error in the meantime. |
@plugwash Is that something that mirrordirector would/should be doing? |
I think it's the mirror itself doing it. plugwash@thinkpad:~$ wget http://ftp.igh.cnrs.fr/pub/os/linux/raspbian/raspbian/pool/main/t/triggerhappy/triggerhappy_0.5.0-1.1_armhf.deb triggerhappy_0.5.0- 100%[===================>] 28.32K --.-KB/s in 0s 2022-01-13 14:32:10 (78.2 MB/s) - ‘triggerhappy_0.5.0-1.1_armhf.deb’ saved [28996/28996] plugwash@thinkpad:~$ plugwash@thinkpad:~$ wget --no-hsts http://ftp.igh.cnrs.fr/pub/os/linux/raspbian/raspbian/pool/main/t/triggerhappy/triggerhappy_0.5.0-1.1_armhf.deb triggerhappy_0.5.0- 100%[===================>] 28.32K --.-KB/s in 0.001s 2022-01-13 15:30:08 (38.2 MB/s) - ‘triggerhappy_0.5.0-1.1_armhf.deb.1’ saved [28996/28996] plugwash@thinkpad:~$ |
On the one hand my current policy is that mirrors should not be doing this because it breaks older versions of apt, OTOH I expect this behavior will get increasingly common on mirrors over time (as part of the general push towards https that is happening in the world) and I may revise my position on this once stretch drops out of LTS (stretch was the last release where apt needed apt-transport-https to support https retreival). So I think pi-gen should handle this case. |
Ah, many thanks for clearing it up. Didn't think that would be something a mirror could do or apt would allow. The fix will show up with the next release. |
this fixed the issue for me, now seeing other errors (unrelated IMO):
|
Fixes RPi-Distro#424 (cherry picked from commit 40f67ce)
Fixes RPi-Distro#424 (cherry picked from commit 40f67ce)
i have this issues in every utunbu os, raspberry pi os, please help me! i use all of : build.sh or build-docker.sh but not solve
The text was updated successfully, but these errors were encountered: