-1250 is a GnuTLS failure "GNUTLS_E_UNIMPLEMENTED_FEATURE" returned by gnutls_certificate_set_x509_system_trust().
Due to a bug, this is output instead of the real number of certs loaded. The fallback code tries to open /etc/ssl/certs to search for certificates. But it seems, this doesn't exist on your system. Regards, Tim On 16.05.20 19:15, Stephen Kirby wrote: > Hi all, > > Tim let me know I only responded to him instead of the list. My bad and > thanks for noticing! So here is what I sent Tim the other day -- > > Thanks all for you inputs! > > I just tried adding the --debug flag and get one more piece of info: > certificates loaded: -1250 > > I am not seeing this error code on a quick search. Maybe someone on the > list knows what it means?. > > Thanks for the strace suggestion. I do see it on the phone emulator and am > thinking next I would run an strace on my Debian Linux system where my wget > is working and compare it to the strace on the mobile emulator where wget > is failing. > > thanks, > Steve > > On Sat, May 16, 2020 at 5:24 AM Tim Rühsen <[email protected]> wrote: > >> Hi Stephen, >> >> please answer to the mailing list, so everybody can participate :) >> >> Regards, Tim >> >> On 15.05.20 20:22, Stephen Kirby wrote: >>> Thanks all for you inputs! >>> >>> I just tried adding the --debug flag and get one more piece of info: >>> certificates loaded: -1250 >>> >>> Any idea what this code means? >>> >>> It does look like the emulator has strace. I will check this as well... >>> >>> thanks, >>> Steve >>> >>> On Fri, May 15, 2020 at 12:07 PM Tim Rühsen <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> On 15.05.20 19:08, Stephen Kirby wrote: >>> > Petr/Everyone, >>> > >>> > Thanks so much for your detailed recommendations on how to >>> proceed. You >>> > were spot on regarding gnutls_priority_set_direct. I looked at >>> config.log >>> > and noticed configure was failing due to a missing pthread lib. I >>> inserted >>> > that, then had to fix some other missing symbols. Anyway, I have a >>> > statically linked wget that I have now pushed onto the Google Pixel >>> > Emulated phone I have running via Android Studio. >>> > >>> > I can definitely move this question to another forum if you all >>> believe it >>> > better since it involves an emulated Google Pixel phone now >>> (x86_64 arch.), >>> > but it has to do with wget still, so if I may please: >>> > >>> > on the emulated phone, I am trying: >>> > >>> > wget -O filename http://###.##.###.## (i.e., here I use the IP >> address >>> > found via nslookup on the named URL) >>> > >>> > Then, I get: >>> > HTTP request sent, awaiting response... 302 object moved >>> > Location: https://(here it lists the correctly named URL) >>> > Resolving (named URL)... Failed: Name or Server not known >>> > wget: unable to resolve host address "named URL" >>> > >>> > I'll note that this wget call works perfectly on my Debian Linux >>> > system, downloading the file I need. >>> > Also interesting to me is the fact that I can ping _successfully_ >>> both the >>> > URL by name or its associated IP address, on the emulated phone >>> So, not >>> > sure why wget would throw this error. >>> >>> wget uses getaddrinfo(), except you built it with c-ares. >>> >>> Perhaps you have 'strace' installed !? >>> Then you could start wget with strace and see what fails (or why >>> getaddrinfo fails). >>> >>> Regards, Tim >>> >> >>
signature.asc
Description: OpenPGP digital signature
