Re: Seamonkey 2.40 and SVG exploit

On 12/6/2016 7:50 AM, NFN Smith wrote: > NoOp wrote: > >>> >> >> My SeaMonkey profile is a little over 10GB with some files going back >> over 15 years. I have many POP3 and IMAP email addresses - several >> having both POP3 and IMAP - many RSS feeds, and a huge nntp >> collection/subscription fr

Re: Seamonkey 2.40 and SVG exploit

Gérard wrote on 12/06/2016 04:59 PM: NFN Smith wrote on 12/06/2016 04:50 PM: NoOp wrote: My SeaMonkey profile is a little over 10GB with some files going back over 15 years. I have many POP3 and IMAP email addresses - several having both POP3 and IMAP - many RSS feeds, and a huge nntp coll

Re: Seamonkey 2.40 and SVG exploit

NFN Smith wrote on 12/06/2016 04:50 PM: NoOp wrote: My SeaMonkey profile is a little over 10GB with some files going back over 15 years. I have many POP3 and IMAP email addresses - several having both POP3 and IMAP - many RSS feeds, and a huge nntp collection/subscription from news.mozilla.

Re: Seamonkey 2.40 and SVG exploit

NoOp wrote: My SeaMonkey profile is a little over 10GB with some files going back over 15 years. I have many POP3 and IMAP email addresses - several having both POP3 and IMAP - many RSS feeds, and a huge nntp collection/subscription from news.mozilla.support, news.gmain.org, news.eternal-sep

Re: Seamonkey 2.40 and SVG exploit

those are test only & I certainly don't want to have them all point to a single profile. O.K., to each their own! -- Daniel User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 SeaMonkey/2.40 Build identifier: 20160120202951 or User agent: Mozilla/5.0 (X11; Linux

Re: Seamonkey 2.40 and SVG exploit

On 12/5/2016 10:40 PM, Daniel wrote: > On 6/12/2016 3:22 PM, NoOp wrote: > > >> Gary >> (as a PS: I do basically the same on linux to set up TB there as well - >> only I usually grsync the SeaMonkey profile from Windows to linux first) >> > Why bother?? I have SM installed on both my Win7 and my

Re: Seamonkey 2.40 and SVG exploit

of my Win7 partitions and just point my Linux SM to the same location. -- Daniel User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 SeaMonkey/2.40 Build identifier: 20160120202951 or User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 SeaMonkey/2.38 Build

Re: Seamonkey 2.40 and SVG exploit

On 12/5/2016 9:18 AM, NFN Smith wrote: > NoOp wrote: >> On 12/2/2016 2:30 PM, NFN Smith wrote: ... >>> me, a temporary move from Seamonkey to Firefox isn't a huge thing, >>> but having to relocate my mail to Thunderbird is more painful, as I >>> still do nearly everything through POP. >> >> Thunder

Re: Seamonkey 2.40 and SVG exploit

e after the move from gecko engine to goanna engine. I still use Thunderbird 24.7 and will not upgrade. Of all my many browsers, the ONLY one that is completely reliable for everything is the final version of the original Opera (12.18). SeaMonkey 2.40 works well also so I will not upgrade it until ther

Re: Seamonkey 2.40 and SVG exploit

NoOp wrote: On 12/2/2016 2:30 PM, NFN Smith wrote: I'm watching discussions relating to the SVG exploit, and am a little confused about what steps I should take. - Use one of Adrian Kalla's unofficial builds? If so, which build, and what potential problems are there? Yes, 2.47

Re: Seamonkey 2.40 and SVG exploit

nnounced a long time ago, but it seems now that we need 2.47 which is not officially released yet So WHAT ? Back everything up, download an unofficial release of SM from https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/ uninstall SeaMonkey 2.40, install the new version W

Re: Seamonkey 2.40 and SVG exploit

s now that we need 2.47 which is not officially released yet So WHAT ? Back everything up, download an unofficial release of SM from https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/ uninstall SeaMonkey 2.40, install the new version We looks like an ass that see

Re: Seamonkey 2.40

On 12/04/2016 06:26 PM, Pat Connors wrote: Thank you, Walt, One more thing, if I just do not use 2.40 till it gets fixed or replaced, do I have to totally remove it from my computer while I use another program? No SeaMonkey 2.40 has not been patched to fix this known security

Re: Seamonkey 2.40

Thank you, Walt, One more thing, if I just do not use 2.40 till it gets fixed or replaced, do I have to totally remove it from my computer while I use another program? SeaMonkey 2.40 has not been patched to fix this known security vulnerability. All including Edge are subject to unknown

Re: Seamonkey 2.40 and SVG exploit

> So given the results ... it appears to me that Adrian has > indeed patched those builds agains the exploit. Thanks! Lee On 12/4/16, NoOp wrote: > On 12/4/2016 10:16 AM, Lee wrote: > >> >> nit: has anyone that _knows_ said that the Dec 1 version of SeaMonkey >> 2.47 has the patch for that exp

Re: Seamonkey 2.40

comm-release-windows32/seamonkey-2.47.en-US.win32.installer.exe> and <https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows32/lightning-5.2.en-US.win32.xpi> 3. Exit SeaMonkey 2.40. 4. Install the downloaded seamonkey-2.47.en-US.win32.installer.

Re: Seamonkey 2.40

urity vulnerability. SeaMonkey 2.40 has not been patched to fix this known security vulnerability. All including Edge are subject to unknown security vulnerabilities until discovered and patched. -- Visit Pittsburgh <http://www.visitpittsburgh.com/> Coexist <https://www.coexist.

Re: Seamonkey 2.40 and SVG exploit

On 12/4/2016 2:49 PM, Richmond wrote: > Richmond writes: > >> In this thread there are some test cases: >> >> https://bugzilla.mozilla.org/show_bug.cgi?id=1321066 >> > > I cannot get Aurora to crash today. I am not sure why. But some of the > tests show that the address sanitizer has trapped som

Re: Seamonkey 2.40 and SVG exploit

Richmond writes: > In this thread there are some test cases: > > https://bugzilla.mozilla.org/show_bug.cgi?id=1321066 > I cannot get Aurora to crash today. I am not sure why. But some of the tests show that the address sanitizer has trapped something. So maybe having a build with debugging stops

Re: Seamonkey 2.40 and SVG exploit

On 12/4/2016 2:25 PM, Richmond wrote: > NoOp writes: > >> On 12/4/2016 11:50 AM, Richmond wrote: >>> NoOp writes: >>> >>> (See comments: 84, 85, and 86 - which for some reason have been marked as 'offtopic' by ryanvm) >>> >>> Because the bug report is for firefox, not seamonkey. >>>

Re: Seamonkey 2.40

Okay, I am totally confused about what I should do or not do. I am thinking of not using 2.40 and instead use Microsoft Edge until SeaMonkey does it update. Question, should I completely erase 2.40 or does just not using it keep my computer safe? Will 2.40 email be safe or if I use Thunderbir

Re: Seamonkey 2.40 and SVG exploit

NoOp writes: > On 12/4/2016 11:50 AM, Richmond wrote: >> NoOp writes: >> >> >>> (See comments: 84, 85, and 86 - which for some reason have been marked >>> as 'offtopic' by ryanvm) >> >> Because the bug report is for firefox, not seamonkey. >> > > Sorry, but I disagree: > > Product: Core

Re: Seamonkey 2.40 and SVG exploit

On 12/4/2016 11:33 AM, NoOp wrote: > On 12/4/2016 10:16 AM, Lee wrote: > >> >> nit: has anyone that _knows_ said that the Dec 1 version of SeaMonkey >> 2.47 has the patch for that exploit? > > I tested Adrian's 2.47's per bug report: > https://bugzilla.mozilla.org/show_bug.cgi?id=1321066 > (See

Re: Seamonkey 2.40 and SVG exploit

On 12/4/2016 11:50 AM, Richmond wrote: > NoOp writes: > > >> (See comments: 84, 85, and 86 - which for some reason have been marked >> as 'offtopic' by ryanvm) > > Because the bug report is for firefox, not seamonkey. > Sorry, but I disagree: Product:Core Shared components used by Fi

Re: Seamonkey 2.40 and SVG exploit

thing up, download an unofficial release of SM from https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/ uninstall SeaMonkey 2.40, install the new version We looks like an ass that sees before him a carrot at the end of a stick Yeah.. using an unofficial version of SeaMonke

Re: Seamonkey 2.40 and SVG exploit

On 12/02/2016 03:30 PM, NFN Smith wrote: I'm watching discussions relating to the SVG exploit, and am a little confused about what steps I should take. I'm one of the users that has stayed with 2.40, and for the most part, I'm content to wait until a new release comes through the normal update

Re: Seamonkey 2.40 and SVG exploit

e after the move from gecko engine to goanna engine. I still use Thunderbird 24.7 and will not upgrade. Of all my many browsers, the ONLY one that is completely reliable for everything is the final version of the original Opera (12.18). SeaMonkey 2.40 works well also so I will not upgrade it until t

Re: Seamonkey 2.40 and SVG exploit

NoOp writes: > (See comments: 84, 85, and 86 - which for some reason have been marked > as 'offtopic' by ryanvm) Because the bug report is for firefox, not seamonkey. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://list

Re: Seamonkey 2.40 and SVG exploit

On 12/4/2016 10:16 AM, Lee wrote: > > nit: has anyone that _knows_ said that the Dec 1 version of SeaMonkey > 2.47 has the patch for that exploit? I tested Adrian's 2.47's per bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1321066 (See comments: 84, 85, and 86 - which for some reason h

Re: Seamonkey 2.40 and SVG exploit

On 12/4/16, Richmond wrote: > Lee writes: > > >> Can Firefox or SeaMonkey automatically update on your machine? If yes >> you're running with admin privs and are _not_ practicing safe >> anything. >> > > That isn't quite true. If you are running firefox on windows you can > install the mozilla up

Re: Seamonkey 2.40 and SVG exploit

ee to upgrade to a version where the SVG exploit is not possible, nit: has anyone that _knows_ said that the Dec 1 version of SeaMonkey 2.47 has the patch for that exploit? > BUT give us an officially released version . The official build system still doesn't work :( > We are stuck with

Re: Seamonkey 2.40 and SVG exploit

Lee writes: > Can Firefox or SeaMonkey automatically update on your machine? If yes > you're running with admin privs and are _not_ practicing safe > anything. > That isn't quite true. If you are running firefox on windows you can install the mozilla update service and it will update firefox. (

Re: Seamonkey 2.40 and SVG exploit

Lee wrote on 04-12-16 17:18: On 12/4/16, Desiree wrote: On 12/3/2016 3:30 AM, TCW wrote: On Fri, 2 Dec 2016 15:30:53 -0700, NFN Smith wrote: I'm watching discussions relating to the SVG exploit, and am a little confused about what steps I should take. <.. snip ..> Use the Adrian Kalla

Re: Seamonkey 2.40 and SVG exploit

On 12/4/16, Desiree wrote: > On 12/3/2016 3:30 AM, TCW wrote: >> On Fri, 2 Dec 2016 15:30:53 -0700, NFN Smith >> wrote: >> >>>I'm watching discussions relating to the SVG exploit, and am a little >>>confused about what steps I should take. >>> <.. snip ..> >> >> Use the Adrian Kalla build. Seri

Re: Seamonkey 2.40 and SVG exploit

and will not upgrade. Of all my many browsers, the ONLY one that is completely reliable for everything is the final version of the original Opera (12.18). SeaMonkey 2.40 works well also so I will not upgrade it until there is an OFFICIAL version available via internal push and I may not upgrade ev

Re: Seamonkey 2.40 and SVG exploit

On 12/3/16, Pat Connors wrote: > I am so confused! > > I get it that 2.40 SeaMonkey has some problems, not sure what they are > other than vulnerabilities. I'd say that's plenty enough of a problem. The latest 0day has example code posted, so the script kiddies have it -- which is probably why w

Re: Seamonkey 2.40 and SVG exploit

On 03/12/2016 20:47, Pat Connors wrote: > I am so confused! > > I get it that 2.40 SeaMonkey has some problems, not sure what they are > other than vulnerabilities. Someone said to 'Turn off javascript' but > do not know how to do so. > > Others are saying to use a later release not yet on Sea

Re: Seamonkey 2.40 and SVG exploit

I am so confused! I get it that 2.40 SeaMonkey has some problems, not sure what they are other than vulnerabilities. Someone said to 'Turn off javascript' but do not know how to do so. Others are saying to use a later release not yet on SeaMonkey site and not use 2.40 at all. Okay, I think

Re: Seamonkey 2.40 and SVG exploit

EE writes: > I am using a Tinderbox build of SM 2.47 quite happily. It works for > me pretty well. It is also dated Dec 2, so hopefully has a patched > Firefox core in it. Also, some of the bugs that were present in 2.40 > are gone. In this thread there are some test cases: https://bugzilla.

Re: Seamonkey 2.40 and SVG exploit

NoOp wrote: On 12/2/2016 2:30 PM, NFN Smith wrote: I'm watching discussions relating to the SVG exploit, and am a little confused about what steps I should take. I'm one of the users that has stayed with 2.40, and for the most part, I'm content to wait until a new release comes through the nor

Re: Seamonkey 2.40 and SVG exploit

Maybe it would help to set image.animation_mode = none ? I can't find anything which says one way or another. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey 2.40 and SVG exploit

On 03/12/2016 10:10, Ant wrote: > Is it confirmed that v2.40 will get a patch? Also, I suppose even SM 2.47 is vulnerable? Or was that the reason for the Dec 1 update, Adrian? Regards. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla

Re: Seamonkey 2.40 and SVG exploit

On 12/2/2016 6:15 PM, NoOp wrote: On 12/2/2016 2:30 PM, NFN Smith wrote: I'm watching discussions relating to the SVG exploit, and am a little confused about what steps I should take. I'm one of the users that has stayed with 2.40, and for the most part, I'm content to wait until a new releas

Re: Seamonkey 2.40 and SVG exploit

On 12/2/2016 2:30 PM, NFN Smith wrote: > I'm watching discussions relating to the SVG exploit, and am a little > confused about what steps I should take. > > I'm one of the users that has stayed with 2.40, and for the most > part, I'm content to wait until a new release comes through the > normal

Seamonkey 2.40 and SVG exploit

I'm watching discussions relating to the SVG exploit, and am a little confused about what steps I should take. I'm one of the users that has stayed with 2.40, and for the most part, I'm content to wait until a new release comes through the normal update channel, although I am concerned about t

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

On Saturday, November 19, 2016 at 9:52:07 AM UTC-7, Chris Ilias wrote: > On 2016-11-17 2:16 AM, pth@gmail.com wrote: > > > My impression is that the microsoft November update rollup makes seamonkey > > 2.46 for windows 7 x32 crash. > > Does the Mozilla Crash Reporter come up? If not, it coul

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

On Friday, November 18, 2016 at 10:15:05 AM UTC-7, Frank-Rainer Grahl wrote: > ... > What I meant with crashing the browser is the Windows telemetry which > came standard with Windows 10 and is now rolled out by Microsoft for 7 > and 8.1 users. It can not be disabled but you can uninstall

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

On Friday, November 18, 2016 at 10:15:05 AM UTC-7, Frank-Rainer Grahl wrote: > > > What I meant with crashing the browser is the Windows telemetry which > came standard with Windows 10 and is now rolled out by Microsoft for 7 > and 8.1 users. It can not be disabled but you can uninstall it.

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

On 2016-11-17 2:16 AM, pthf1n...@gmail.com wrote: My impression is that the microsoft November update rollup makes seamonkey 2.46 for windows 7 x32 crash. Does the Mozilla Crash Reporter come up? If not, it could be because you're not using an official release. If it does, 1. Open SeaMonkey

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

On 11/19/2016 at 3:26 AM, Frank-Rainer Grahl's prodigious digits fired off: Yes but the Windows update catalog is different. If you want to actually get a kb from it you need to use an MS browser. And KB3197867 for Windows 7 or KB3197873 for 8.1 are only available there. FRG Ed Mullen wrote:

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

You can't do a thing about it in Windows 10. Spying is build so deeply into it it can not be removed. Using the privacy options will not fully disable it. And it gets worse with every release. You can hack it but with the Anniversary edition I gave up and just wiped the vm. When my other older T

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

Yes but the Windows update catalog is different. If you want to actually get a kb from it you need to use an MS browser. And KB3197867 for Windows 7 or KB3197873 for 8.1 are only available there. FRG Ed Mullen wrote: You do NOT need to use IE or Edge to view Knowledge Base atricles. Just Go

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

Frank-Rainer Grahl wrote on 18-11-16 18:14: Submitting telemetry data is disabled by default in SeaMonkey. Telemetry itself is so woven into the gecko engine that you will see fragments of it even when disabled. But no data is transmitted. What I meant with crashing the browser is the Windows

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

On 11/18/2016 at 12:35 PM, Larry S.'s prodigious digits fired off: So how do I get KB3197867? In Windows Update Catalog I get a brief flash of the content, then "There is a problem with this site" (or equivalent). No way to get at the download. Advice greatly appreciated. Larry S. Just Google

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

On 11/18/2016 at 12:43 PM, Frank-Rainer Grahl's prodigious digits fired off: You need to use IE. Also close all other browsers. AS siad they make it hard to get rid of this... FRG Larry S. wrote: Frank-Rainer Grahl wrote: Submitting telemetry data is disabled by default in SeaMonkey. Telemetr

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

Ray_Net wrote: EE wrote on 17-11-16 19:56: Frank-Rainer Grahl wrote: Works fine fro me in x86 and x64 with 2.46 and 2.47. The latest Windows 7 update includes telemetry by default and I have seen at least one report were this crashed the browser. Monst/any problems you will have with SeaMonkey

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

You need to use IE. Also close all other browsers. AS siad they make it hard to get rid of this... FRG Larry S. wrote: Frank-Rainer Grahl wrote: Submitting telemetry data is disabled by default in SeaMonkey. Telemetry itself is so woven into the gecko engine that you will see fragments of it

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

Frank-Rainer Grahl wrote: Submitting telemetry data is disabled by default in SeaMonkey. Telemetry itself is so woven into the gecko engine that you will see fragments of it even when disabled. But no data is transmitted. What I meant with crashing the browser is the Windows telemetry which came

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

Submitting telemetry data is disabled by default in SeaMonkey. Telemetry itself is so woven into the gecko engine that you will see fragments of it even when disabled. But no data is transmitted. What I meant with crashing the browser is the Windows telemetry which came standard with Windows 1

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

On Thursday, November 17, 2016 at 1:27:07 AM UTC-7, Frank-Rainer Grahl wrote: > > could anyone explain in plain english, what is happening with Seamonkey for > > windows 7 ? Please? > > > We are having build problesmw which delayed the next release for a few > weeks now. They are in the process o

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

EE wrote on 17-11-16 19:56: Frank-Rainer Grahl wrote: Works fine fro me in x86 and x64 with 2.46 and 2.47. The latest Windows 7 update includes telemetry by default and I have seen at least one report were this crashed the browser. Monst/any problems you will have with SeaMonkey you will likely

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

Curious, will version also work on Windows 10 in x64? For Windows x86 pick 2.46 from here: https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows32/ My impression is that the microsoft November update rollup makes seamonkey 2.46 for windows 7 x32

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

Frank-Rainer Grahl wrote: Works fine fro me in x86 and x64 with 2.46 and 2.47. The latest Windows 7 update includes telemetry by default and I have seen at least one report were this crashed the browser. Monst/any problems you will have with SeaMonkey you will likely also have with Firefox. Same

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

could anyone explain in plain english, what is happening with Seamonkey for windows 7 ? Please? We are having build problesmw which delayed the next release for a few weeks now. They are in the process of being fixed but it takes time and the devs are all volunters which have a life. For Windo

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

On 11/17/2016 08:16 AM, pthf1n...@gmail.com wrote: On Tuesday, June 21, 2016 at 5:18:49 PM UTC-6, pthf...@gmail.com wrote: SeaMonkey continues to have some issues, for example, often when I hit the browser's Back button to go to previous webpage, nothing happens. Very frequent. Is 2.40 the fi

Re: Is "SeaMonkey 2.40" the last version, or will there be further updates?

On Tuesday, June 21, 2016 at 5:18:49 PM UTC-6, pthf...@gmail.com wrote: > SeaMonkey continues to have some issues, > > for example, often when I hit the browser's Back button to go to previous > webpage, nothing happens. Very frequent. > > Is 2.40 the final version, or will there be future upda

Re: Seamonkey 2.40 and GMail

On Wednesday, October 19, 2016 at 12:03:46 AM UTC+10, WaltS48 wrote: > Remove the check mark for "Advertise Firefox compatibility". > > REF: Thank you. Worked. ___ support-seamonkey mai

Re: Seamonkey 2.40 and GMail

On Sunday, October 16, 2016 at 8:01:47 PM UTC-4, Cruz, Jaime wrote: > Just started seeing a message when I go to the GMail website: This > version of Firefox is no longer supported, please upgrade your browser. > > Not sure when this started happening though. > > -- > Jaime A. Cruz > President

Re: Seamonkey 2.40 and GMail

Cruz, Jaime wrote: Just started seeing a message when I go to the GMail website: This version of Firefox is no longer supported, please upgrade your browser. Not sure when this started happening though. I had not been to the Gmail site for a while - I POP Gmail to SM. I just went to Gmail, go

Re: Seamonkey 2.40 and GMail

Le 19/10/2016 21:09, NFN Smith a écrit : Personally, I prefer using POP for my primary usage, and where I keep my stores of mail going back nearly 20 years. It is possible to move some messages from an IMAP hierarchy of folders to the equivalent hierarchy in the local folders space, you just

Re: Seamonkey 2.40 (latest stable) uses NSS 3.20.1 - possible security vulnerability

seemonkey wrote: But it would close the vulnerability in nss. If one would release a seamonkey let's say 2.40.1 only with the change of nss 3.21.1 the result would be the same as i described. I didn't mention any bug in the base product. The whole topic was started with nss and not bugs/sec vu

Re: Seamonkey 2.40 (latest stable) uses NSS 3.20.1 - possible security vulnerability

s in latest firefox esr /45.4.0/ and > >>>>> also in latest thunderbird /45.4.0/) > >>>>> > >>>>> As a workaround i can copy the nss libraries from firefox esr to > >>>>> seamonkey > >>>>> until a security

Re: Seamonkey 2.40 and GMail

Ed Mullen wrote: On 10/19/2016 at 12:05 PM, Cruz, Jaime's prodigious digits fired off: sean.nat...@invalid.knights.nee wrote: just a question, why bother "logging in" to their websites at all, when Seamonkey will download via pop or imap? i mean, i have 12 e'mail addresses all being downloade

Re: Seamonkey 2.40 and GMail

Ed Mullen wrote: > On 10/19/2016 at 12:05 PM, Cruz, Jaime's prodigious digits fired off: >> sean.nat...@invalid.knights.nee wrote: >> >>> just a question, why bother "logging in" to their websites at all, when >>> Seamonkey will download via pop or imap? >>> >>> i mean, i have 12 e'mail addresses a

Re: Seamonkey 2.40 and GMail

On 10/19/2016 at 12:05 PM, Cruz, Jaime's prodigious digits fired off: sean.nat...@invalid.knights.nee wrote: just a question, why bother "logging in" to their websites at all, when Seamonkey will download via pop or imap? i mean, i have 12 e'mail addresses all being downloaded via imap just so

Re: Seamonkey 2.40 and GMail

On 10/19/2016 12:05 PM, Cruz, Jaime wrote: sean.nat...@invalid.knights.nee wrote: just a question, why bother "logging in" to their websites at all, when Seamonkey will download via pop or imap? i mean, i have 12 e'mail addresses all being downloaded via imap just so i never have to spend time

Re: Seamonkey 2.40 and GMail

sean.nat...@invalid.knights.nee wrote: just a question, why bother "logging in" to their websites at all, when Seamonkey will download via pop or imap? i mean, i have 12 e'mail addresses all being downloaded via imap just so i never have to spend time logging into webmail pages. Because that'

Re: Seamonkey 2.40 (latest stable) uses NSS 3.20.1 - possible security vulnerability

Frank-Rainer Grahl wrote on 18/10/2016 22:03: I wouldn't start hacking together a version with different binaries. Might work might not. And this won't close any bugs in the base product which could be exploited if you are so concerned about security. Ok, I will stay with my official SM 2.40 wi

Re: Seamonkey 2.40 (latest stable) uses NSS 3.20.1 - possible security vulnerability

and >>>>> also in latest thunderbird /45.4.0/) >>>>> >>>>> As a workaround i can copy the nss libraries from firefox esr to seamonkey >>>>> until a security release of seamonkey let's say 2.40.1 arrives. I tried >>>>> this en

Re: Seamonkey 2.40 and GMail

On 10/16/2016 08:01 PM, Cruz, Jaime wrote: Just started seeing a message when I go to the GMail website: This version of Firefox is no longer supported, please upgrade your browser. Not sure when this started happening though. Remove the check mark for "Advertise Firefox compatibility". RE

Re: Seamonkey 2.40 and GMail

NFN Smith wrote: sean.nat...@invalid.knights.nee wrote: just a question, why bother "logging in" to their websites at all, when Seamonkey will download via pop or imap? i mean, i have 12 e'mail addresses all being downloaded via imap just so i never have to spend time logging into webmail page

Re: Seamonkey 2.40 (latest stable) uses NSS 3.20.1 - possible security vulnerability

es. I tried > >>> this end i can start seamonkey with newer NSS library because they're > >>> compatible. > >> "As a workaround i can copy the nss libraries from firefox esr to > >> seamonkey " > >> > >> Could you tell us what w

Re: *Resolved* - Seamonkey 2.40 and GMail

sean.nat...@invalid.knights.nee wrote: > Jonathan N. Little wrote: >> Cruz, Jaime wrote: >>> SamuelS wrote: Pat Connors wrote: > I started getting also. > >> Just started seeing a message when I go to the GMail website: This >> version of Firefox is no longer supported, please

Re: Seamonkey 2.40 and GMail

sean.nat...@invalid.knights.nee wrote: just a question, why bother "logging in" to their websites at all, when Seamonkey will download via pop or imap? i mean, i have 12 e'mail addresses all being downloaded via imap just so i never have to spend time logging into webmail pages. A good questi

Re: Seamonkey 2.40 (latest stable) uses NSS 3.20.1 - possible security vulnerability

;>>> this end i can start seamonkey with newer NSS library because they're >>>> compatible. >>> "As a workaround i can copy the nss libraries from firefox esr to >>> seamonkey " >>> >>> Could you tell us what we need (in details

Re: Seamonkey 2.40 and GMail

ey're complaining. However, I have my working profile tweaked enough that I'm not able to log into either of those sites, either in Safe Mode, or by using browser spoofing (showing Firefox 49). I know that with Seamonkey 2.40, the "advertise Firefox compatibility" shows Firefox

Re: Seamonkey 2.40 and GMail

On 10/16/2016 at 11:29 PM, myhrd...@gmail.com's prodigious digits fired off: On Sunday, October 16, 2016 at 7:01:47 PM UTC-5, Cruz, Jaime wrote: Just started seeing a message when I go to the GMail website: This version of Firefox is no longer supported, please upgrade your browser. Not sure wh

Re: *Resolved* - Seamonkey 2.40 and GMail

Jonathan N. Little wrote: Cruz, Jaime wrote: SamuelS wrote: Pat Connors wrote: I started getting also. Just started seeing a message when I go to the GMail website: This version of Firefox is no longer supported, please upgrade your browser. -- Pat Connors http://www.connorsgenealogy.com

Re: Seamonkey 2.40 and GMail

re complaining. However, I have my working profile tweaked enough that I'm not able to log into either of those sites, either in Safe Mode, or by using browser spoofing (showing Firefox 49). I know that with Seamonkey 2.40, the "advertise Firefox compatibility" shows Firefox 43.0

Re: *Resolved* - Seamonkey 2.40 and GMail

Cruz, Jaime wrote: > SamuelS wrote: >> Pat Connors wrote: >>> I started getting also. >>> Just started seeing a message when I go to the GMail website: This version of Firefox is no longer supported, please upgrade your browser. >>> >>> >>> -- Pat Connors http://www.connorsgenealogy.com >

Re: *Resolved* - Seamonkey 2.40 and GMail

SamuelS wrote: Pat Connors wrote: I started getting also. Just started seeing a message when I go to the GMail website: This version of Firefox is no longer supported, please upgrade your browser. -- Pat Connors http://www.connorsgenealogy.com Pat - thank you, this solution worked. Thank

Re: Seamonkey 2.40 and GMail

I started getting also. Just started seeing a message when I go to the GMail website: This version of Firefox is no longer supported, please upgrade your browser. -- Pat Connors http://www.connorsgenealogy.com ___ support-seamonkey mailing list sup

Re: Seamonkey 2.40 and GMail

On Sunday, October 16, 2016 at 7:01:47 PM UTC-5, Cruz, Jaime wrote: > Just started seeing a message when I go to the GMail website: This > version of Firefox is no longer supported, please upgrade your browser. > > Not sure when this started happening though. > > -- > Jaime A. Cruz > President

Seamonkey 2.40 and GMail

Just started seeing a message when I go to the GMail website: This version of Firefox is no longer supported, please upgrade your browser. Not sure when this started happening though. -- Jaime A. Cruz President Nassau Wings Motorcycle Club http://www.nassauwings.org/ AMA District 34 http://www

Re: Seamonkey 2.40 (latest stable) uses NSS 3.20.1 - possible security vulnerability

with newer NSS library because they're compatible. "As a workaround i can copy the nss libraries from firefox esr to seamonkey " Could you tell us what we need (in details) to do ? I have Firefox 46.0.1 and SeaMonkey 2.40 on a windows pc. Upgrade. The current version of Firefox is

Re: Seamonkey 2.40 (latest stable) uses NSS 3.20.1 - possible security vulnerability

security release of seamonkey let's say 2.40.1 arrives. I tried >> this end i can start seamonkey with newer NSS library because they're >> compatible. > > "As a workaround i can copy the nss libraries from firefox esr to > seamonkey " > > Could

Re: Seamonkey 2.40 (latest stable) uses NSS 3.20.1 - possible security vulnerability

. "As a workaround i can copy the nss libraries from firefox esr to seamonkey " Could you tell us what we need (in details) to do ? I have Firefox 46.0.1 and SeaMonkey 2.40 on a windows pc. ___ support-seamonkey mailing list support-sea

Re: Seamonkey 2.40 (latest stable) uses NSS 3.20.1 - possible security vulnerability

WaltS48 wrote: On 10/14/2016 08:49 PM, Edward wrote: TCW wrote: On Wed, 12 Oct 2016 23:06:52 -0700 (PDT), seemonkey12...@gmail.com wrote: There's at least one security vulnerability that is missing from this NSS version: http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1950 There w

Re: Seamonkey 2.40 (latest stable) uses NSS 3.20.1 - possible security vulnerability

On 10/14/2016 08:49 PM, Edward wrote: TCW wrote: On Wed, 12 Oct 2016 23:06:52 -0700 (PDT), seemonkey12...@gmail.com wrote: There's at least one security vulnerability that is missing from this NSS version: http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1950 There was a bugfix in

Re: Seamonkey 2.40 (latest stable) uses NSS 3.20.1 - possible security vulnerability

On Saturday, October 15, 2016 at 2:49:48 AM UTC+2, Edward wrote: > TCW wrote: > > On Wed, 12 Oct 2016 23:06:52 -0700 (PDT), seemonkey > > wrote: > > > >> There's at least one security vulnerability that is missing from this NSS > >> version: http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-20

  1   2   3   >