On 4/13/2016 2:07 PM, Mason83 wrote:
On 12/04/2016 13:37, Richard Owlett wrote:

On 4/11/2016 3:48 PM, Paul in Houston, TX wrote:

(It will be many years before I up from 2.26.1.  It always works
flawlessly.)

Wondered if I was only one using a working SeaMonkey <grin>
I haven't heard anyone mention any feature of interest in the
more current releases.
I've been following this group regularly for > 4 years.
YMMV

<rolls eyes>

The MAIN feature of newer releases is: security fixes

Yes, I may have been called curmudgeon *BUT* I read your sentence as saying that _no_ feature of interest has been added since 2.26.1 .


Here's a list of known vulnerabilities affecting older
versions of Seamonkey.

https://www.mozilla.org/en-US/security/known-vulnerabilities/seamonkey/

That list doesn't even attempt to make your point.
The bug titles chosen give little hint as to what user is vulnerable.
I clicked on the first ~10 links.
Most explicitly reported a JavaScript problem or included "In general this flaw cannot be exploited through email in the Thunderbird product because scripting is disabled, but is potentially a risk in browser or browser-like contexts." I explicitly surf with JavaScript and cookies disabled. Is there any other "scripting" I should be aware of? If so the site is faulty for giving no hint of it.

One title ["URL spoofing in reader mode"] hinted at a possible problem. https://www.mozilla.org/en-US/security/advisories/mfsa2015-103/ gives no hint as to what is "reader" mode. https://bugzilla.mozilla.org/show_bug.cgi?id=1195976 doesn't do any better. A web search reveals "reader mode" is peculiar to "mobile devices". I don't own one. Therefore another irrelevant bug.

BTW https://validator.w3.org/ reports https://bugzilla.mozilla.org/show_bug.cgi?id=1195976 as having 57 Errors and 15 warnings.





Regards.

_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to