Use NoScript [noscript.net] to block Optimizely, Google Tag Manager, etc. from running their untrusted/undesirable javascript in your FireFox browser.

It looks intelligible to me, the problem is maybe that the first component is followed by a list? If you read it out loud it's fine but I can see it might be confusing if you assume The Register is part of a list.

[Zoom, the BBC, CNN, HSBC, and numerous other websites briefly served malware on November 16th.].

I'd say it's unambiguous because if you assume the first comma is part of a list, the sentence no longer makes sense.

In a recent development, something ? something ? something : something ? something : something : something.

for English. There's only one way to interpret that validly (let's not talk about PHP...), and a compiler will do so. But it's an ugly way to express logic and most good programmers will use linebreaks and parentheses.

I would agree your fixes would improve the summary's sentence and yes in gener.

It looks unambiguous to me, but then again, I had college level reading in grade school.

Industry observers note that it's the news. They should have written it for idiots. Like you. I agree.

According to recent reports, scott's blog was careful to not that these websites did not use Content Security Policy (CSP) or that they did so poorly and that had they done so correctly it would have blocked the bad guys. Sometime security is very hard, sometimes it is basic competence.

This was a failure of basic competence. Obviously many major websites failed this step. There is little doubt that countless other websites omit or screw up this basic protection.

Zoom and Salesforce are supposed to be tech companies, right? And they're including JS from foreign servers without integrity checks? Then they got exactly what they deserve. Anyone including third-party JavaScript without integrity checks has already self-pwned. ...and Optimizely requires it so they can basically supply-chain-attack you AS THEIR BUSINESS MODEL.

They did not get exactly what they deserved. They only got egg on their faces. As usual, the people who got the short end of the stick were the users.

Sources indicate that I think though the attitude you're expressing is pervasive in the industry, and probably why devs don't see things like "Use a proper programming language rather than a glorified assembler" as applying to them. After all, it's they that'll get embarrassed if a security flaw is found, rather than their users who'll suffer when they have their credit card number.

This hit way more than 178 sites. Our site was infected with this crap, and has not been reported on any of the lists of infected sites. We're not small ($1.5-$2M/day in online sales) but we're way smaller than most of the victims that have been publicly named. I'd guess that thousands of sites were affected by this.

There may be more comments in this discussion. Without JavaScript enabled, you might want to turn on Classic Discussion System in your preferences instead.

In a recent development, dynamically binding, you realize the magic. Statically binding, you see only the hierarchy.

→ Read original article