Leased lines
Given it allegedly involves a corrupted database, used to authenticate subscribers, I'm not surprised it affects non-leased lines.
C.
3533 publicly visible posts • joined 21 Sep 2011
"I feel like this article is not quite up to the Reg's usual bar of quality, what with the copious spelling and grammatical errors and misinformation."
Argh, ok, we'll go back over it. It was a Friday afternoon piece - but that's no excuse.
C.
Just like software written by professionals has bugs, articles written and edited by professionals have errors from time to time. It's fixed.
As for the Intel U/M thing. It's a Kaby Lake R Intel Core M part, but has a U in the part name. Because Intel.
From the official spec sheet, the 8550U is a Kaby Lake R part as opposed to a Kaby Lake U or a Skylake U.
Chipzilla's naming of stuff drives me bonkers.
C.
"The majority of the Russian ad spend happened AFTER the election"
Yeah, something like 56% after, 44% before.
Fact-Checking a Facebook Executive’s Comments on Russian Interference
A Reg reader falling for a SV exec's spin? Oh my days.
C.
All right, GrumpyReaper. I think you're being overly pedantic. Half the article stresses that home hardware can't handle the high-speeds, and that 1Gbps is more than enough let alone 10Gbps.
We assume all Reg readers are smart enough to understand that YMMV when discussing theoretical maximum data transfer speeds. Since you're being so pedantic, consider this: we didn't say anything about _writing_ the data to disk, merely fetching it. So yes, you can download a 25GB game in a few seconds over a 10Gbps line - writing it to storage is another thing entirely, which Reg readers know all too well.
I've tweaked the piece to make it crystal clear.
C.
I dunno man, I spent 80 bucks on an Apple wireless mouse for my work MacBook Pro, and I sure feel like I've been taxed like an idiot. Same goes for the RAM and other accessories I've bought for my home Mac gear over the many many many many
many many many many many
many
many many many many many many many many years.
C.
(Yes, El Reg hacks use Macs. That's part of the joke. We also have a new rule that you have to split your time between macOS / Linux and Windows, so we get the same daily experience of crap technology our readers face.)
"So the fact that it now happens to go a bit further is no problem, and not an error"
Who said it was a problem? We're just pointing out that it's overshot. Musk tweeted the final burn was going to send the thing "to Mars". It was heading to Mars. It's going to miss Mars by a much greater distance than expected.
Christ, it's a flying PR st- car. A flying car in space. It's funny as fuck.
Jeez, tough crowd! ;-)
C.
At the time of writing, it was suspected the engines ran out of fuel. We weren't invited to the press conference. Can't think why. Anyway, it ran out of ignitor, so... close enough, ish. We've tweaked the article and another piece is coming.
C.
"True, I suspect security was pretty low on the list in the '70s when the original 8086 was designed"
The security hole was introduced way after the 8086. Basically, Intel and others screwed up. They're trying to spin this away as a design side effect.
Like a plane crashing mid-flight is a side effect of a substantial fuel tank leak.
C.
"Well, to be fair to Intel, they perfected prefetch as a performance boost..."
I think you missed the point of my post. I meant Meltdown/Spectre reveals an embarrassing cockup in Intel's processor designs (and Arm, AMD, etc for Spectre). Yeah yeah, prefetching and speculative exec and branch prediction speeds stuff up. That wasn't the point of my post.
The point is that chip engineers left security in the glovebox the day they parked up in the company lot and walked in to design those parts of the pipeline.
It's like a manager told them: "Speed. Security. Price. Pick one."
C.
>"Secrets" ? Who wants those "secrets" ? Does the "other end" even know I've got any "secrets" ?
By secrets, I mean: passwords and personal information. And yes, you have them in your computer. This is why it's good to patch - when good patches arrive, natch.
>Show me proof people are being attacked, left and right, thanks to Spectre and Meltdown.
No one's said people are. Relax guy. You're overreacting.
C.
"I mean, what's the probability for me to become a target ?"
Spectre is irritating because it's hard to fix and lets software read stuff it shouldn't. This means JavaScript in the browser can sniff out secrets from the kernel and other tabs. There are PoC exploits for this out there. It's important for ppl to update their stuff, hence the attention on the flaws.
Likewise Meltdown: malware will be along to lift stuff out of the kernel.
PS: For us, the biggest thing about it is the embarrassing design cockup and the messy fixes, rather than this being the total end of the world (because it isn't).
C.
>It DOES NOT not prevent your ISP from tracking sites or pages you visit.
It does prevent ISPs from tracking pages. All the ISP sees is an encrypted connection to, say, a Wikipedia server. It has no idea which pages I'm reading.
And I'm not so sure about your other claims, either.
C.
Big publications – from the NYT with its huge army of copy editors to the Grauniad with a sizable editing team - still let through errors. We have 3 region editors (North America, Europe, APAC), 1 news editor (UK) and 1 sub-editor (UK).
It's frankly fucking amazing there aren't more errors slipping through on El Reg given the resources available. The current rate is pretty low. It's hard to find good editors who can do sperlinng, snarky headlines, and are experts in tech and science.
C.
Due to a technical cockup, an old draft of the piece went live instead of the final edit. We keep a history of all article revisions, and an early revision overwrote the latest one.
I just restored the final edit. The piece was edited hours ahead of publication, and set to go live at 8am PT / 4pm UTC. We don't publish stuff straight to the web - it gets edited by at least one editor.
Basically, someone with a browser tab open with an old version of the story clicked on 'save and close', rather than 'close', in our web publishing system, and overwrote the clean version. Oops. But it's fixed.
Don't forget to email corrections@theregister.com if you spot anything wrong.
C.