On 12/01/2016 10:12 AM, NoOp wrote: > On 12/01/2016 08:40 AM, Lee wrote: >> On 12/1/16, TCW <"."> wrote: >>> On 11/30/2016 8:06 AM, WaltS48 wrote: >>>>> There's a zero-day exploit in the wild that's being used to execute >>>>> malicious code on the computers of people using Tor and possibly other >>>>> users of the Firefox browser, officials of the anonymity service >>>>> confirmed Tuesday. >>>>> >>>> >>>>> The versions span from 41 to 50, with version 45 ESR being the version >>>>> used by the latest version of the Tor browser. >>>> >>>> <http://arstechnica.com/security/2016/11/firefox-0day-used-against-tor-users-almost-identical-to-one-fbi-used-in-2013/> >>>> >>>> >>>> Is a fix for SeaMonkey needed? >>> >>> Looks like Adrian has applied it to his 2.47 build @ >>> http://tinyurl.com/j2ju4s7. >> >> Would you please not post obfuscated URLs? Especially now, in a >> thread about a 0day & probably most everybody reading the thread >> running exploitable software, enticing people to click on random links >> is a really bad idea. >> >> $ curl -s --head http://tinyurl.com/j2ju4s7 | grep Location >> Location: >> https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows32/ >> >> Thanks, >> Lee >> > > Mine updated from 2.46 to2.46 - however on the Windows 10 systems I'm > getting crashes from these builds:
Correction: ...from 2.46 to 2.47 (release update channel)... _______________________________________________ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
