I don't think all that testing is necessary based on the timeline I posted previously, but I did it anyway.
I just downgraded NoScript to 2.9.0.14 on FF 50 for Windows, and removed the new ABE rule. Dashlane works perfectly. The only ABE notice in the console is
Code: Select all
[ABE WAN] Detected WAN IP <my public IP address>
which does not seem to be of any significance.
I then updated NoScript back to 2.9.5.1. Dashlane no longer works. All the ABE Deny errors are in the console again:
Code: Select all
[ABE] < LOCAL> Deny on {GET http://127.0.0.1:17896/ <<< about:blank - 1}
SYSTEM rule:
Site LOCAL
Accept from LOCAL
Deny
If it's true that about:blank is not local, then my guess is there was a bug or oversight in NoScript that treated it as if it is, and that hole was sealed in 2.9.5. But this exposed the problem with Dashlane - and perhaps there are other extensions that do something similar?
I don't think all that testing is necessary based on the timeline I posted previously, but I did it anyway.
I just downgraded NoScript to 2.9.0.14 on FF 50 for Windows, and removed the new ABE rule. Dashlane works perfectly. The only ABE notice in the console is
[code][ABE WAN] Detected WAN IP <my public IP address>[/code]
which does not seem to be of any significance.
I then updated NoScript back to 2.9.5.1. Dashlane no longer works. All the ABE Deny errors are in the console again:
[code]
[ABE] < LOCAL> Deny on {GET http://127.0.0.1:17896/ <<< about:blank - 1}
SYSTEM rule:
Site LOCAL
Accept from LOCAL
Deny[/code]
If it's true that about:blank is not local, then my guess is there was a bug or oversight in NoScript that treated it as if it is, and that hole was sealed in 2.9.5. But this exposed the problem with Dashlane - and perhaps there are other extensions that do something similar?