Justin Wood (Callek) wrote:
Desiree wrote:
"WaltS" <wls15...@removeyahoo.com> wrote in message
news:ofmdnsxm8p1ohxdnnz2dnuvz_uidn...@mozilla.org...
On 10/28/2012 02:30 PM, Ant wrote:
On 10/28/2012 10:44 AM PT, WaltS typed:
...
http://www.seamonkey-project.org/ shows it out. I will wait for its
internal updater. :)
I downloaded the 32-bit version, and installed it.
Checking for updates using the 64-bit version didn't seem to find an
update, and it may not since it is a contributed build.
Ah. I am using 32-bit from Mozilla's server and still no updates just a
few minutes ago. https://bugzilla.mozilla.org/show_bug.cgi?id=805714
says it is waiting for Symantec/Norton's whitelist before releasing the
internal update. Let's hope this works correctly. ;)
How's that 64-bit one? Can you tell any differences from the 32-bit one?
It looks prettier.
--
Fedora 17 (64-bit)
Thunderbird Beta (17.0) Install and test it.
One state should not determine an election.
http://www.nationalpopularvote.com/
I must have missed something along the way regarding this. I read the bug
and I still don't understand what Norton's whitelist has to do with
releasing the SM update.
It's Tuesday and still no update available through internal updater.
Its out now.
The short answer re: Nortons whitelist, is that there are a good number of users
of SeaMonkey using Norton as a Virus Scan.
Norton has "heuristic" scans, which are falsely identifying some files SeaMonkey
needs to function properly as "including behavior that is known/common in
malware" (or some such), which makes Norton (by default, with little way to
prevent in future installs) delete the files from the OS.
Even restoring them from Norton yields future problems with partial-updates
(since norton, seems to slightly modify the checksum of the dll's when restored)
SeaMonkey will still startup when this happens for most users, but many
essential functions are broken.
It is why I still made SeaMonkey available via the website, since users who
manually download/install can recognize the issue relatively easily; however
users who get an update automatically, and then on restart get it applied, only
to find out Norton hurt their install will have had issues, without easily
understanding what the issue was.
None of the Sec Issues fixed in SM 2.13.2 were exploited in the wild (that we
know of yet), so I felt safe in the wait for Norton here.
Thank you for the explanation, I know a few people I suspect of using Windows.
--
Bill Davidsen <david...@tmr.com>
We are not out of the woods yet, but we know the direction and have
taken the first step. The steps are many, but finite in number, and if
we persevere we will reach our destination. -me, 2010
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
