My pleasure, Jim Hurley. I like puzzles.
Just an extra observation without wanting to tell you how to run your own system, but it might help any others reading the thread:
NoScript has other security functions that run under the hood.
They are to my mind even more important in many cases than blocking scripts and embeddings. That's where NS really does "have my back". Clickjacking protection, ABE patrolling application boundaries, enforcing https, anti-XSS protection (not the faux one that IE runs).
So if I find a page like this messy one, and I really must view content, I am safer choosing "Globally Allow" from the NS menu and staying with NoScript in Firefox than I would be if I ran IE or any other modern browser. Even if NS only points out a Clickjack or two, it's been worth it.
NoScript has a lot of coding that anticipates trouble. No other script using browsers do this.
Here endeth the NS lesson
Just an extra observation without wanting to tell you how to run your own system, but it might help any others reading the thread:
NoScript has other security functions that run under the hood.
They are to my mind even more important in many cases than blocking scripts and embeddings. That's where NS really does "have my back". Clickjacking protection, ABE patrolling application boundaries, enforcing https, anti-XSS protection (not the faux one that IE runs).
So if I find a page like this messy one, and I really must view content, I am safer choosing "Globally Allow" from the NS menu and staying with NoScript in Firefox than I would be if I ran IE or any other modern browser. Even if NS only points out a Clickjack or two, it's been worth it.
NoScript has a lot of coding that anticipates trouble. No other script using browsers do this.
Here endeth the NS lesson
