Firefox 60.1esr NoScript

Ask for help about NoScript, no registration needed to post
swoop
Posts: 2
Joined: Thu Jun 28, 2018 9:04 am

Firefox 60.1esr NoScript

Post by swoop »

Hello,

i updated Firefox to 60.1esr, now it is not possible to open the web-ui to my storage (https, selfsigned certificate).
NoScript means it has to filter scripts but i have set his IP to TRUSTED.

Is there anything i can do?
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
User avatar
Giorgio Maone
Site Admin
Posts: 9546
Joined: Wed Mar 18, 2009 11:22 pm
Location: Palermo - Italy
Contact:

Re: Firefox 60.1esr NoScript

Post by Giorgio Maone »

Do you mean you cannot add the IP and then turn the HTTPS lock to green?
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
swoop
Posts: 2
Joined: Thu Jun 28, 2018 9:04 am

Re: Firefox 60.1esr NoScript

Post by swoop »

hello,

thanks for the quick reply.

when i hit "trust", i found out the address is not added to the per-site-permissions
even when i add it manualy, with or without green lock, it would not display the page.

i foud one other device in my network with a similar phenomenon.
when i browse to my firewalls web-ui with ip-address then i could add the ip-adress to per-site-perminssions via the NoScript-Button,
when i browse to the same device via hostname (https://firewall/) then i coult not add the Adress to the per-site-permissions with the button, even i add it manualy, it didnt recognise the scripts,
when i browse to the exakt same device via fwdn (https://firewall.domain.tld) then the butten is working correctly again.

BTW: i use Windows 10 Build 16299.492
Last edited by barbaz on Thu Jun 28, 2018 4:25 pm, edited 1 time in total.
Reason: kill board-generated links
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
barbaz
Senior Member
Posts: 11138
Joined: Sat Aug 03, 2013 5:45 pm

Re: Firefox 60.1esr NoScript

Post by barbaz »

known issue https://forums.informaction.com/viewtop ... =7&t=24627
As a workaround, try whitelisting the full address manually in NoScript Options.
*Always* check the changelogs BEFORE updating that important software!
-
Post Reply