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:

User agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:50.0) Gecko/20100101
Build identifier: 20161201093907


User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0)
Gecko/20100101 Firefox/50.0 SeaMonkey/2.47
Build identifier: 20161201025712

I can repeat the crashes on two separate Windows machines just by trying
to reply to an email or nntp post. Works OK on Linux:

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101
Firefox/50.0 SeaMonkey/2.47
Build identifier: 20161201022155

which is what I am replying from for this post.

Ping Adrian: please look at the crash reports.
support-seamonkey mailing list

Reply via email to