Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 43 |
Nodes: | 6 (0 / 6) |
Uptime: | 96:24:15 |
Calls: | 290 |
Files: | 904 |
Messages: | 76,426 |
There is no truly correct answer to that question. Here's my $0.02: I
always want to run the latest release of a web browser -- otherwise
you're counting on folks to be able to identify every single patch
related to security and backport it -- even if people are trying. This
is why I run the rapid slot of Firefox.
The ESR is officially supported by Mozilla, so you don’t rely on only
one person (from Nebraska) here.
So which slot should I choose? Any opinions out there?
Hi Rainer,
On 5/12/24 00:35, Dr Rainer Woitok wrote:
So which slot should I choose? Any opinions out there?
I can't speak for Firefox, but I do maintain Chromium which is similar
enough in terms of being a browser with a fast release cycle and several channels.
I recommend keeping your browser as up-to-date as possible. The `rapid` channel for Firefox may result in more frequent updates for you as
an end-user, but it always includes the latest fixes (and features)
That's not saying that ESR is likely to be vulnerable, but the fixes
going into ESR are going to be backported from the rapid and development channels. A lot of work goes into ensuring that these backports are done
in a timely manner, but it's not beyondthe realm of possibility for one
to be missed, or announced and fixed in rapid but not in ESR leaving
those users vulnerable.
IMO if you're not an enterprise you should be running rapid. If you are
an enterprise you have your own requirements to think about, but you
should probably also be running rapid.
In Chromium terms, I often run the beta (or dev) channels, as I know
that security fixes for the stable channel are implemented in dev
and backported from there.
I hope that helps, I need to run and get breakfast.
Cheers,
Matt