Re: armhf: buster: TLS / HTTPS partly broken

From	<tomas@tuxteam.de>
Newsgroups	linux.debian.user
Subject	Re: armhf: buster: TLS / HTTPS partly broken
Date	2020-05-04 14:00 +0200
Message-ID	<A2HVo-2FT-3@gated-at.bofh.it> (permalink)
References	<A2r4e-U3-9@gated-at.bofh.it> <A2DI6-fF-7@gated-at.bofh.it> <A2Eb8-pD-13@gated-at.bofh.it> <A2HVo-2FT-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Mon, May 04, 2020 at 01:49:34PM +0200, Mark Jonas wrote:
> Hi Reco,
> 
> > > > Ok. Can you run tcpdump while you're running curl?
> > > > Specifically,
> > > >
> > > > tcpdump -s0 -pnni any -w /tmp/curl.pcap tcp port 443
> > >
> > > I tried to dump from within the running container but failed.
> >
> > It's way too complicated. Docker is basically a one big NAT, so please
> > run tcpdump on a host instead.
> 
> I used the identical image to run the container on an amhf host
> (Raspberry Pi 3). So there is now no QEMU in the way.
> 
> > But this hiccup gave me an idea - maybe libssl on armhf is perfectly
> > fine, but it's qemu which fails to emulate certain CPU instruction.
> 
> 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.

Of course this may be a bad idea for a permanent "solution", but would
allow you to bisect the problem.

Cheers
-- t

Thread

Re: armhf: buster: TLS / HTTPS partly broken Mark Jonas <toertel@gmail.com> - 2020-05-04 09:30 +0200
  Re: armhf: buster: TLS / HTTPS partly broken Reco <recoverym4n@enotuniq.net> - 2020-05-04 10:00 +0200
    Re: armhf: buster: TLS / HTTPS partly broken <tomas@tuxteam.de> - 2020-05-04 14:00 +0200
      Re: armhf: buster: TLS / HTTPS partly broken Mark Jonas <toertel@gmail.com> - 2020-05-04 14:40 +0200
        Re: armhf: buster: TLS / HTTPS partly broken tomas@tuxteam.de - 2020-05-04 15:20 +0200
          Re: armhf: buster: TLS / HTTPS partly broken Mark Jonas <toertel@gmail.com> - 2020-05-04 20:40 +0200
    Re: armhf: buster: TLS / HTTPS partly broken Mark Jonas <toertel@gmail.com> - 2020-05-04 14:00 +0200
      Re: armhf: buster: TLS / HTTPS partly broken Reco <recoverym4n@enotuniq.net> - 2020-05-04 14:20 +0200
        Re: armhf: buster: TLS / HTTPS partly broken Mark Jonas <toertel@gmail.com> - 2020-05-04 20:50 +0200
          Re: armhf: buster: TLS / HTTPS partly broken Reco <recoverym4n@enotuniq.net> - 2020-05-05 07:00 +0200
            Re: armhf: buster: TLS / HTTPS partly broken Mark Jonas <toertel@gmail.com> - 2020-05-05 08:10 +0200
              Re: armhf: buster: TLS / HTTPS partly broken Reco <recoverym4n@enotuniq.net> - 2020-05-05 08:30 +0200
                Re: armhf: buster: TLS / HTTPS partly broken Mark Jonas <toertel@gmail.com> - 2020-05-05 08:50 +0200
                Re: armhf: buster: TLS / HTTPS partly broken Andrei POPESCU <andreimpopescu@gmail.com> - 2020-05-05 09:20 +0200
                Re: armhf: buster: TLS / HTTPS partly broken Michael Howard <mike@dewberryfields.co.uk> - 2020-05-05 09:20 +0200
                Re: armhf: buster: TLS / HTTPS partly broken Mark Jonas <toertel@gmail.com> - 2020-05-05 16:10 +0200
                Re: armhf: buster: TLS / HTTPS partly broken Reco <recoverym4n@enotuniq.net> - 2020-05-05 09:30 +0200
                Re: armhf: buster: TLS / HTTPS partly broken Mark Jonas <toertel@gmail.com> - 2020-05-05 16:50 +0200
              Re: armhf: buster: TLS / HTTPS partly broken Greg Wooledge <wooledg@eeg.ccf.org> - 2020-05-05 13:40 +0200
                Re: armhf: buster: TLS / HTTPS partly broken Mark Jonas <toertel@gmail.com> - 2020-05-05 16:40 +0200
                Re: armhf: buster: TLS / HTTPS partly broken Greg Wooledge <wooledg@eeg.ccf.org> - 2020-05-05 17:10 +0200
                Re: armhf: buster: TLS / HTTPS partly broken Mark Jonas <toertel@gmail.com> - 2020-05-05 17:50 +0200

csiph-web