PM x64 33.x crash with noscript

General discussion about the NoScript extension for Firefox
Locked
User avatar
cartel
Junior Member
Posts: 49
Joined: Sun Jul 14, 2013 11:31 pm

PM x64 33.x crash with noscript

Post by cartel »

both 33 versions do it. 32.5.2 doesnt
been using noscript over 10 years and never had issues before
PM will not crash when noscript is disabled

https://9xbuddy.in/process?url=https%3A ... 1456915718

this link I click
Image

windows 7

Faulting application name: palemoon.exe, version: 6.6.0.8791, time stamp: 0x65b36ab8
Faulting module name: xul.dll, version: 6.6.0.8791, time stamp: 0x65b36c84
Exception code: 0xc0000005
Fault offset: 0x0000000000849dff
Faulting process id: 0xf28
Faulting application start time: 0x01da6cb65d63a83c
Faulting application path: C:\Program Files\Pale Moon\palemoon.exe
Faulting module path: C:\Program Files\Pale Moon\xul.dll

Image

then to top it off I get these popovers without noscript and when I try to inspect element it redirects the developer tools to debugger.

https://forum.palemoon.org/download/fil ... =18545&t=1

the popover spam is blocked by noscript and I am protected




the tiktok link is blocked

Image

I allow it the video plays:

Image

the popover spam is blocked by noscript and I am protected
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:77.0) Gecko/20100101 Firefox/77.0
User avatar
cartel
Junior Member
Posts: 49
Joined: Sun Jul 14, 2013 11:31 pm

Re: PM x64 33.x crash with noscript

Post by cartel »

I tried to get help at PM forum but was stonewalled:
by Moonchild » Sat Mar 02, 2024 11:31 am
Cartel you've been around here for a very long time now with almost 500 posts to your name.
Why on earth are you still not understanding we... do... not... support... installations... with... NoScript?
It is well-known it causes stability issues, not in the least because it can block browser-internal scripts literally breaking the application. Yes that includes appcrashes. Undefined behaviour with blocked components or components having been yanked out from under a running script driving the UI can also lead to exploitable security issues (??).
I been using noscript for over 10 years, closer to 15 years and its been something I cant live without.
I never had a virus in all this time.
The alternative umatrix just doent cut it and is confusing and annoying.

I guess I have no choice but to not update my browser anymore
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:77.0) Gecko/20100101 Firefox/77.0
User avatar
therube
Ambassador
Posts: 7938
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: PM x64 33.x crash with noscript

Post by therube »

Use SeaMonkey (where NoScript still works).
Use older version of PM (where NoScript still works).

Wait, if it ever happens, until PM changes something to where NoScript works again (without crashing on video).
And a link to the PM threads would have been nice.

Even the thread where they were some were offering to pay for a "fixed" NoScript (& even if they, instead of being glad that NoScript exists, still harped on it).


I'm glad NoScript exits - in all its incarnations.
Thank you. :-).
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.19
User avatar
cartel
Junior Member
Posts: 49
Joined: Sun Jul 14, 2013 11:31 pm

Re: PM x64 33.x crash with noscript

Post by cartel »

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:77.0) Gecko/20100101 Firefox/77.0
User avatar
therube
Ambassador
Posts: 7938
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: PM x64 33.x crash with noscript

Post by therube »

Just so you know, if you change the NoScript's "GUID" (in install.rdf, in noscript...xpi), NoScript will install in current PaleMoon.


"Install" does not change any potential negative consequences (like PM crashing), but at least it can be used, till then ;-).


Something like this does the trick:

STEVENscript-5.1.9rc1+THERUBE (to bypass PM block on NoScript ;- )).xpi:

Code: Select all

   <em:id>{73a6fe31-595d-460b-a920-fcc0f8842121}</em:id>
   <em:name>STEVENScript 5.1.9rc1+HACK</em:name>
Here, [link removed by barbaz]
SHA1: B7EADF321D136CB948E20CC676FDBA06B4D4D329



BTW, don't bother going to the PM forums for help ;-).
Last edited by barbaz on Fri May 31, 2024 11:57 pm, edited 1 time in total.
Reason: Remove link
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.19
barbaz
Senior Member
Posts: 10860
Joined: Sat Aug 03, 2013 5:45 pm

Re: PM x64 33.x crash with noscript

Post by barbaz »

therube wrote: Fri May 31, 2024 3:10 pm Just so you know, if you change the NoScript's "GUID" (in install.rdf, in noscript...xpi), NoScript will install in current PaleMoon.


"Install" does not change any potential negative consequences (like PM crashing),
... but OP started this thread because they do get the crash, so in their case the block list entry for NoScript is 100% called for, so how does this help? Image

Crashes can greatly increase attack surface. Are you REALLY sure this crash isn't exploitable?

The only reason to circumvent the block list is if you're trying to troubleshoot/diagnose/fix the crash & want to reproduce it without disabling the block list. That change is *not* for end-users who just want to use NoScript. I removed the link to the ready-modified XPI, since the only people for whom such change might be constructive would find it trivial to do it themselves.

Even if the crash can be stopped, are we sure NoScript Classic would even work in current Pale Moon? UXP has surely changed a lot in the last years, has anyone actually tested NoScript Classic in current Pale Moon? A false sense of security is worse than no sense of security.
*Always* check the changelogs BEFORE updating that important software!
Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0
User avatar
therube
Ambassador
Posts: 7938
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: PM x64 33.x crash with noscript

Post by therube »

NoScript is not supported on PM, they won't even talk to you if you have it installed.
That is known.

AFAIK, it works (though with the latest versions of PM, it is apt to crash PM [video related, seemingly]...).

(Not really concerned about it one way or the other, but IMO NoScript is just something you don't leave home without. So that it can be made to work in PM, regardless of crashing or support, that's good enough for me.)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.19
User avatar
therube
Ambassador
Posts: 7938
Joined: Thu Mar 19, 2009 4:17 pm
Location: Maryland USA

Re: PM x64 33.x crash with noscript

Post by therube »

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.19
barbaz
Senior Member
Posts: 10860
Joined: Sat Aug 03, 2013 5:45 pm

Re: PM x64 33.x crash with noscript

Post by barbaz »

Locking for staff review.
*Always* check the changelogs BEFORE updating that important software!
Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0
Locked