On Mon, May 04, 2020 at 02:39:09PM +0200, Mark Jonas wrote: > Hi Thomas, > > > > curl https://www.google.com still fails on the armhf host. So QEMU is > > > out of the game. > > > > Someone hinted at ca_certificates. To verify that, you could try with > > the option "-k" for curl. Then the server certificate isn't checked. > > Yes, "curl -k https:/www.google.com" succeeds. Then it's quite probable that the problem lies with certificate resolution. Either it doesn't find a trusted root cert to validate the server against, or the validation fails. You might try curl's -v option (with and without -k) to see whether it sheds some light. Also the proposal brought on this list of looking at strace. Perhaps limit the trace to file operations, like so: strace -f -e trace=%file -o trace.out <your curl command here> This would let you see where curl is looking for certs files. Cheers -- t
Attachment:
signature.asc
Description: Digital signature