From nobody Thu Oct 10 16:30:46 2024 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XPZxj1ty7z5ZGK7 for ; Thu, 10 Oct 2024 16:30:49 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from mailout.qeng-ho.org (mailout.qeng-ho.org [217.155.128.244]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPZxh2krfz54cR for ; Thu, 10 Oct 2024 16:30:48 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of freebsd@qeng-ho.org designates 217.155.128.244 as permitted sender) smtp.mailfrom=freebsd@qeng-ho.org; dmarc=none Received: from [IPV6:2a02:8010:64c9:1::2] (unknown [IPv6:2a02:8010:64c9:1::2]) by mailout.qeng-ho.org (Postfix) with ESMTP id 5AE593E2BC; Thu, 10 Oct 2024 17:30:46 +0100 (BST) Message-ID: <65eb8b64-3273-4215-a493-ff670cba6729@qeng-ho.org> Date: Thu, 10 Oct 2024 15:30:46 -0100 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Firefox 131 failing all https connections To: Paul Procacci , FreeBSD-Questions References: <08566be4-c21f-4074-bae0-3a5f87256c95@qeng-ho.org> Content-Language: en-GB From: Arthur Chance In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-3.29 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_ALLOW(-0.20)[+ip4:217.155.128.240/29]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:13037, ipnet:217.155.0.0/16, country:GB]; FREEMAIL_TO(0.00)[gmail.com,freebsd.org]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; DMARC_NA(0.00)[qeng-ho.org]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4XPZxh2krfz54cR X-Spamd-Bar: --- On 10/10/2024 15:22, Paul Procacci wrote: > > > On Thu, Oct 10, 2024 at 11:59 AM Arthur Chance > wrote: > > I've just upgraded to Firefox 131 (131.0_1,2 to be precise) and I can > only access http pages and any attempt to fetch an https page fails with > an empty page. The web developer tools simply show the unhelpful > NS_ERROR_FAILURE for the fetch. > > With the previous version (FF 129) everything worked correctly. I have > the ca_root_nss pkg installed, but asking FF 131 about root certificates > shows many expired ones so I suspect it's somehow failing to pick up the > certificates from the pkg. > > Any suggestions where I go from here? > > > Current OS: > > > uname -a > FreeBSD arthur.home.qeng-ho.org > 13.3-RELEASE-p7 FreeBSD 13.3-RELEASE-p7 > GENERIC amd64 > > Firefox build options from poudriere: > > ===> The following configuration options are available for > firefox-131.0_1,2: >      CANBERRA=off: Sound theme alerts >      DBUS=on: D-Bus IPC system support >      DEBUG=off: Build with debugging support >      FFMPEG=on: FFmpeg support (WMA, AIFF, AC3, APE...) >      LIBPROXY=off: Proxy support via libproxy >      LTO=off: Use Link-Time Optimization >      OPTIMIZED_CFLAGS=on: Use extra compiler optimizations >      PROFILE=off: Build with profiling support >      TEST=off: Build and/or run tests > ====> Extra cubeb audio backends (OSS is always available) >      ALSA=off: ALSA audio architecture support >      JACK=off: JACK audio server support >      PULSEAUDIO=off: PulseAudio sound server support >      SNDIO=off: Sndio audio support > > > -- > Although not designed for computation, PIO is quite likely Turing > complete, provided a long enough piece of tape can be found. It is > conjectured that it could run DOOM, given a sufficiently high clock > speed.  — The Raspberry Pi Pico datasheet on its PIO capability. > > > Two things come to mind. > > 1) Is the date/time correct on your machine? chronyc tells me this machine is 19 microseconds slow from the correct time. Close enough. :-) > 2) Do you have the latest nss package installed? arthur@arthur[4]▶ pkg info -x ca_root ca_root_nss-3.104 > > When this happens to me, granted not very often, it's usually because my > date/time wasn't synced. -- Although not designed for computation, PIO is quite likely Turing complete, provided a long enough piece of tape can be found. It is conjectured that it could run DOOM, given a sufficiently high clock speed. — The Raspberry Pi Pico datasheet on its PIO capability.