Might just be that Facebook is randomizing the script sources it actually loads?
↧
Re: Inconsistent Update of Temporarily Allow All This Page
↧
Re: website not working
It works for me just by setting "..laurea.fi" to TRUSTED.
If it doesn't for you, could you please send me your NoScript Options>Export file for examination? Thanks.
If it doesn't for you, could you please send me your NoScript Options>Export file for examination? Thanks.
↧
↧
Re: No More "Temporarily allow all..." Option
Skeezix wrote:That last update was confusing to me. I wonder whose idea it was to hide that option ...
Nobody's. Most likely, an accidental drag&drop.
↧
Re: Bing Untrusted sometimes allowed
Might it just be that in those case the images are static, shown without using any client-side scripting?
When it happens could you check bot the console (ctrl+shift+K) and the page source for hints at what's happening?
When it happens could you check bot the console (ctrl+shift+K) and the page source for hints at what's happening?
↧
Re: google.com and doubleclick.net XSS issue
Also, could you copy & paste the exact message you get in the dialog (it might help to work-around possible false positives)?
↧
↧
Re: (classic) Automatic reload broken?
Any news on the fix?
Also, on a somewhat unrelated note, will the NoScript Classic release that fixes this bug be the final NoScript Classic release?
Also, on a somewhat unrelated note, will the NoScript Classic release that fixes this bug be the final NoScript Classic release?
↧
Re: 5.1.8.7rc4 is not signed
The hack is not likely the issue.
The hack allows you to install unsigned extensions.
If you make a change to the extension itself, & if the extension is signed, your change breaks the signing.
But (by default) extensions do need to be signed to be installed.
So you cannot make changes to extensions & expect them to work.
Well, unless you also remove the signing parts from the extension - or get them signed.
But if you remove the signing parts from the extension, the extension can no longer be installed because then the signing is missing.
But, if you use the hack, signing is not required, so you can make changes to the extension & they can be installed, so long as you remove the signing parts from the extension itself.
So (after backing up first) try removing the /META-INF/ directory from the extension & see if then works.
And again, that also assumes that you have made a change to an extension, which breaks the signing, & that you have something in place, a hack, or you're using some browser that does not require signing at all.
Isn't a bunch of crap that Mozilla makes you go through "for your security" (or whatever their "stated" reasons for putting you through that crap are).
The hack allows you to install unsigned extensions.
If you make a change to the extension itself, & if the extension is signed, your change breaks the signing.
But (by default) extensions do need to be signed to be installed.
So you cannot make changes to extensions & expect them to work.
Well, unless you also remove the signing parts from the extension - or get them signed.
But if you remove the signing parts from the extension, the extension can no longer be installed because then the signing is missing.
But, if you use the hack, signing is not required, so you can make changes to the extension & they can be installed, so long as you remove the signing parts from the extension itself.
So (after backing up first) try removing the /META-INF/ directory from the extension & see if then works.
And again, that also assumes that you have made a change to an extension, which breaks the signing, & that you have something in place, a hack, or you're using some browser that does not require signing at all.
Isn't a bunch of crap that Mozilla makes you go through "for your security" (or whatever their "stated" reasons for putting you through that crap are).
↧
Re: 5.1.8.7rc4 is not signed
Must admit, I do get fed up with a lot of the so called 'security' crap..some of which is totally unnecessary.
This started right after I installed the hack. I hadn't made any other changes either to FF or the add-on itself Is it possible that Mozilla has changed something that is 'breaking' the add-ons and making them corrupt?
I would be interested though on how to reverse the hack anyway just to give me a better understanding of things.
Btw, I'm using FF 55.0.3
Thanks.
This started right after I installed the hack. I hadn't made any other changes either to FF or the add-on itself Is it possible that Mozilla has changed something that is 'breaking' the add-ons and making them corrupt?
I would be interested though on how to reverse the hack anyway just to give me a better understanding of things.
Btw, I'm using FF 55.0.3
Thanks.
↧
Re: No More "Temporarily allow all..." Option
That's what I'm suspecting. ![:oops:]( "Embarrassed")
One last thing - is there a way to edit my thread titles once I have posted the initial thread? Some forums allow that, and I use that to add "Fixed" or "Resolved" to them.
One last thing - is there a way to edit my thread titles once I have posted the initial thread? Some forums allow that, and I use that to add "Fixed" or "Resolved" to them.
↧
↧
Re: No More "Temporarily allow all..." Option
Skeezix wrote:One last thing - is there a way to edit my thread titles once I have posted the initial thread? Some forums allow that, and I use that to add "Fixed" or "Resolved" to them.
Yes. Edit your first post, edit the subject line.
↧
Re: 5.1.8.7rc4 is not signed
Presumably you put two files into the FF installation directory.
Remove them (or rename) & restart FF.
> mozilla.cfg
> autoconfig.js
viewtopic.php?p=98662#p98662
Remove them (or rename) & restart FF.
> mozilla.cfg
> autoconfig.js
viewtopic.php?p=98662#p98662
↧
Re: website not working
It worked with the settings mentioned. I should have thought of that. That was easy way to solve this. Noscript only showed tunnistus.laurea.fi so I only tried to allow that website. Thank you for your help! Oh and sorry for bad explanation.
↧
Re: 5.1.8.7rc4 is not signed
Thanks, I did that but I got an error message stating 'failed to read the config file'
I don't know if it makes a difference but I'm running a portable version of FF
I don't know if it makes a difference but I'm running a portable version of FF
↧
↧
Webfonts
In normal noscript it's possible to enable webfonts (spotify webplayer for example)
NSA version does not have that option.
Any not-obvious way to do that,or is this a feature request?
NSA version does not have that option.
Any not-obvious way to do that,or is this a feature request?
↧
Re: [FIXED] (classic) Automatic reload broken?
Giorgio Maone wrote:I'll try to keep up with security fixes as long as compatible browsers which do receive security updates (such as Palemoon or Waterfox) are still available.
This Pale Moon user is grateful. Thank you very much.
I do have a question:
NoScript's (external) listing seems to have just disappeared again from the Pale Moon add-ons site.
[ https://addons.palemoon.org/extensions/ ]
Is it possible to restore it?
↧
Re: Webfonts
"webfonts" are the "fonts" capability, which is enabled both in the DEFAULT and in the TRUSTED presets out of the box.
If you want to enable it on demand instead, you can uncheck it from the DEFAULT preset and assign a CUSTOM one to the site you want fonts to be loaded.
If you want to enable it on demand instead, you can uncheck it from the DEFAULT preset and assign a CUSTOM one to the site you want fonts to be loaded.
↧
Re: 5.1.8.7rc4 is not signed
mozilla.cfg
"Then firefox will start and you can look at the console"
- try {
// All lines of your code (without "//")
} catch (e) {
Components.utils.reportError(e);
}
"Then firefox will start and you can look at the console"
↧
↧
Re: [FIXED] (classic) Automatic reload broken?
If it is not there, have to assume that PM removed it.
PM is hostile to NoScript, as it is.
PM takes the attitude of no support if you use NoScript.
Also possible that on that page they only list extensions there that "specifically" support PM (not sure)?
PM is hostile to NoScript, as it is.
PM takes the attitude of no support if you use NoScript.
Also possible that on that page they only list extensions there that "specifically" support PM (not sure)?
↧
Re: [FIXED] (classic) Automatic reload broken?
whoosh wrote:Is it possible to restore it?
I sent an email to my "lead" there (the one who published the external listing last time).
↧
Re: Localization NS 10
fatboy wrote:I will return what was before. But it is necessary to forbid this person to break what was done by others.
I can send an email to the translation coordinator for this project. But the "messages.json (Russian)" resource at this moment says "Last updated by fatboy 3 days and 18 hours ago".
So, who's the author of the translation I've merged yesterday into 10.1.9.7rc2? And does it need to be updated again before I release 10.1.9.7 stable?
↧