Hi Andres
> Thanks for the explanation. What happens if you run chromium with
> --tls1 ? That sets the min SSL version to TLSv1.0, although I'm not
> sure what changed within chromium to actually drop TLSv1 support; if
> it's a third party library, then the code to support it might just be
>
Hi Andres
> I'm a bit confused by this bug report. Why do you need chromium
> (presumably over https) talking to network hardware drivers? Or do
> you mean you have older network hardware where the firmware exposes
> an https port, and chromium no longer supports the older SSL
> protocols that
On 2/17/22 02:21, Benoît Panizzon wrote:
Hi Andres
I'm a bit confused by this bug report. Why do you need chromium
(presumably over https) talking to network hardware drivers? Or do
you mean you have older network hardware where the firmware exposes
an https port, and chromium no longer
On Tue, 15 Feb 2022 14:13:38 +0100 Benoit Panizzon wrote:
> Package: chromium
> Version: 98.0.4758.80-1~deb11u1
> Severity: important
> X-Debbugs-Cc: t...@security.debian.org
>
> Dear Maintainer,
>
> It looks like some 'outdated' version of SSL has been completely
disabled with the newest
Package: chromium
Version: 98.0.4758.80-1~deb11u1
Severity: important
X-Debbugs-Cc: t...@security.debian.org
Dear Maintainer,
It looks like some 'outdated' version of SSL has been completely disabled with
the newest update,
without leaving an option to re-enable in chrome://flags
Some network
5 matches
Mail list logo
