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 >

Re: SM update status...

On 12/02/2016 02:21 PM, Adrian Kalla wrote: > W dniu 12/02/2016 o 09:43 PM, Mr. Ed pisze: >> If you want an unofficial 64 bit version of SM you can get it here: >> http://www.m64.info/index.php/seamonkey-64-bit-download > > > I'd recommend to never ever put links to that site anywhere. For many

Re: SM update status...

On 12/02/16 5:21 PM, Adrian Kalla wrote: > W dniu 12/02/2016 o 09:43 PM, Mr. Ed pisze: >> If you want an unofficial 64 bit version of SM you can get it here: >> http://www.m64.info/index.php/seamonkey-64-bit-download > > > I'd recommend to never ever put links to that site anywhere. For many >

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

Re: SM update status...

W dniu 12/02/2016 o 09:43 PM, Mr. Ed pisze: > If you want an unofficial 64 bit version of SM you can get it here: > http://www.m64.info/index.php/seamonkey-64-bit-download I'd recommend to never ever put links to that site anywhere. For many reasons: 1st, because they just take my builds and

Re: SM update status...

Mr. Ed wrote: On 12/02/16 11:26 AM, Paul B. Gallagher wrote: Mr. Ed wrote: This morning when opening SM it automatically downloaded and installed the latest 2.47 (12/01). Really!? My SM 2.40, when asked manually to check for updates, says none are available. Running 2.47 (64 bit with

Re: SM update status...

Mr. Ed wrote: > On 12/01/16 9:31 PM, Mr. Ed wrote: >> On 12/01/16 8:44 PM, sean wrote: >>> Ant wrote: On 12/1/2016 9:08 AM, WaltS48 wrote: > On 12/1/2016 11:59 AM, Ant wrote: >> https://blog.seamonkey-project.org/2016/12/01/face-the-music/ :( > > 2.40 needs patched. 

Re: SM update status...

On 12/02/16 1:15 PM, Lee wrote: > On 12/2/16, Paul B. Gallagher wrote: >> WaltS48 wrote: >>> On 12/02/2016 11:26 AM, Paul B. Gallagher wrote: Mr. Ed wrote: > This morning when opening SM it automatically downloaded and > installed the latest 2.47

Re: SM update status...

On 12/02/16 11:26 AM, Paul B. Gallagher wrote: > Mr. Ed wrote: > >> This morning when opening SM it automatically downloaded and >> installed the latest 2.47 (12/01). > > Really!? > > My SM 2.40, when asked manually to check for updates, says none are available. > Running 2.47 (64 bit with

Re: 0day exploit - Security update for SeaMonkey needed?

Lee wrote: On 12/2/16, Frank-Rainer Grahl wrote: Glad that 2.47 works well but you are likely running Adrians unofficial version :) yes Official one is still stuck in l10n mud. Stuck how?

Re: SM update status...

Felix Miata wrote: sean composed on 2016-12-01 18:44 (UTC-0700): fwiw, 2.49a2 is working perfectly for me... I'm sure our overworked and underpaid volunteers know there's no need to waste time with 2.40... I've almost never used chatzilla & never dom Inspector... so no tears will ever be

Re: 0day exploit - Security update for SeaMonkey needed?

W dniu 12/02/2016 o 08:13 PM, Lee pisze: > >> Official one is still stuck in l10n mud. > > Stuck how? > https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows32/ > has lots of seamonkey-2.47.XX.langpack.xpi files - do they not work, > is it just a

Re: 0day exploit - Security update for SeaMonkey needed?

On 12/2/16, Frank-Rainer Grahl wrote: > Glad that 2.47 works well but you are likely running Adrians unofficial > version :) yes > Official one is still stuck in l10n mud. Stuck how?

Re: SM update status...

On 12/2/16, Paul B. Gallagher wrote: > WaltS48 wrote: >> On 12/02/2016 11:26 AM, Paul B. Gallagher wrote: >>> Mr. Ed wrote: >>> This morning when opening SM it automatically downloaded and installed the latest 2.47 (12/01). >>> >>> Really!? >>> >>> My SM

Re: SM update status...

On 02/12/2016 17:26, Paul B. Gallagher wrote: Mr. Ed wrote: This morning when opening SM it automatically downloaded and installed the latest 2.47 (12/01). Really!? My SM 2.40, when asked manually to check for updates, says none are available. Same for me here in the deep south west of

Re: SM update status...

W dniu 12/02/2016 o 06:05 PM, Paul B. Gallagher pisze: > WaltS48 wrote: >> On 12/02/2016 11:26 AM, Paul B. Gallagher wrote: >>> Mr. Ed wrote: >>> This morning when opening SM it automatically downloaded and installed the latest 2.47 (12/01). >>> >>> Really!? >>> >>> My SM 2.40, when

Re: SM update status...

On 12/02/2016 11:26 AM, Paul B. Gallagher wrote: Mr. Ed wrote: This morning when opening SM it automatically downloaded and installed the latest 2.47 (12/01). Really!? My SM 2.40, when asked manually to check for updates, says none are available. Unless they haven't updated

Re: SM update status...

Mr. Ed wrote: This morning when opening SM it automatically downloaded and installed the latest 2.47 (12/01). Really!? My SM 2.40, when asked manually to check for updates, says none are available. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher

Re: 0day exploit - Security update for SeaMonkey needed?

Glad that 2.47 works well but you are likely running Adrians unofficial version :) Official one is still stuck in l10n mud. FRG Lee wrote: On 12/2/16, Frank-Rainer Grahl wrote: > LOL! I think you meant "everything", but "anything" is probably > jupp. ewong is still

Re: 0day exploit - Security update for SeaMonkey needed?

On 12/2/16, Frank-Rainer Grahl wrote: > > LOL! I think you meant "everything", but "anything" is probably > > > jupp. ewong is still fighting with the 2.46 repacks so best to use > Adrians version right now until this is sorted out. A 2.47 should follow > soon but first 2.46 to

Re: SM update status...

Alex Beauroy wrote: On 02/12/2016 12:54, Mr. Ed wrote: On 12/01/16 9:31 PM, Mr. Ed wrote: On 12/01/16 8:44 PM, sean wrote: Ant wrote: On 12/1/2016 9:08 AM, WaltS48 wrote: On 12/1/2016 11:59 AM, Ant wrote: https://blog.seamonkey-project.org/2016/12/01/face-the-music/ :( 2.40 needs

Re: SM update status...

On 02/12/2016 12:54, Mr. Ed wrote: On 12/01/16 9:31 PM, Mr. Ed wrote: On 12/01/16 8:44 PM, sean wrote: Ant wrote: On 12/1/2016 9:08 AM, WaltS48 wrote: On 12/1/2016 11:59 AM, Ant wrote: https://blog.seamonkey-project.org/2016/12/01/face-the-music/ :( 2.40 needs patched.  Yep, badly!

Re: SM update status...

On 12/01/16 9:31 PM, Mr. Ed wrote: > On 12/01/16 8:44 PM, sean wrote: >> Ant wrote: >>> On 12/1/2016 9:08 AM, WaltS48 wrote: On 12/1/2016 11:59 AM, Ant wrote: > https://blog.seamonkey-project.org/2016/12/01/face-the-music/ :( 2.40 needs patched.  >>> >>> Yep, badly! >> >> fwiw,

Re: 0day exploit - Security update for SeaMonkey needed?

> LOL! I think you meant "everything", but "anything" is probably > jupp. ewong is still fighting with the 2.46 repacks so best to use Adrians version right now until this is sorted out. A 2.47 should follow soon but first 2.46 to get the build bugs out. FRG Lee wrote: On 12/1/16,