On 1/31/2017 12:53 AM, Frank-Rainer Grahl wrote:
> Its about:buildconfig in SeaMonkey and Firefox.
> 
> But this only gives you the changelog for the whole source tree including 
> Thunderbird.
> 
> FRG

Correct. Of course you can compare against the 2.47 build:
<https://hg.mozilla.org/releases/comm-release/rev/4da63141cb902adf573947586a2e52915ad4ebb1>

so I reckon the only way to tell any more is to look at the builds and
compare directly?

There is still no "official" 64bit build for SeaMonkey, so 64bit linux
users are pretty much left to contrib, Adrian's builds, and or
'Ubuntuzilla' builds (which are basically 'contrib' builds).

SeaMonkey meeting minutes seem to be the only place to find info any
longer...

Security information is still on 2.38:

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

At this point my primary concern is security updates. As noted here,
Firefox and Thunderbird have been addressing security issues on a full
time basis:

<https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/>
<https://www.mozilla.org/en-US/security/known-vulnerabilities/thunderbird/>

It would be *very* helpful if you can advise which one of these fixed
bugs address the comparable CVE/security fixes on Firefox and Thunderbird:

<https://bugzilla.mozilla.org/buglist.cgi?o5=notequals&f1=OP&v6=fixed&o3=equals&list_id=8372932&v3=fixed&resolution=FIXED&o6=notequals&o2=equals&f4=CP&v5=fixed&query_format=advanced&j1=OR&f3=cf_status_seamonkey248&f2=target_milestone&f5=cf_status_seamonkey247&v2=2.48>

and advise on the the current known vulnerabilities in 2.46 & which are
addressed in 2.48.

I never thought I'd do this, but I'm actually now starting to tweak
Thundebird UI/Themes so I can use on a full time basis, and using
alternative browsers for the same. I've had to switch all of my clients
from SeaMonkey as we are stuck in time with regards to security
patches/updates.

You know that I appreciate all that you and everyone that contributes to
the SeaMonkey project do, but I just can no longer risk my client's
online security by leaving SeaMonkey installed on their systems.

> 
> Daniel wrote:
> ...
> 
>> Clicking on your about:build gets ....
>> 
>> "Invalid Address
>> 
>> The URL is not valid and cannot be loaded.
>> 
>> The provided address is not in a recognized format. Please check the 
>> location 
>> bar for mistakes and try again."
>> 
>> Maybe that's a FF thing!!
>> 
> 

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

Reply via email to