Posts by diodesign

"bored"

Funny way to spell banned.

C.

Re: The sky is falling in

"Get a life."

Get another site to comment on.

C.

Re: headline

Hmmmm, I thought it was pretty obvious - but happy to make it more clear.

C.

Re: apologist

"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.

Re: On the topic of ultrasound...

"More likely the suppression is happening in the amplifier stage."

OK, I've slightly tweaked that.

C.

Re: Big John

"I'm saying this article is written specifically to attract haters"

Well, no. It was written to highlight failings by a federal regulator's chairman. Scrutiny. Press. You know.

"That's evil."

Don't be so stupid. Why do you hang around here?

C.

Blergh, we walked into that one.

C.

Re: Elsewhere in the media

Yeah, we reported on it in 2016 (Just search El Reg for 'DressCode'). Seems the thing is still around.

C.

Re: Nice PR

Show us on the doll where Google hurt you.

C.

Re: Seriously, whoever wrote this title...

...was me and I respectfully suggest you:

# apt-get install senseofhumor

C.

Re: Mark 85

> Old story that is now surfacing or doesn't the company know what year it is?

No, it means it committed to supporting Pebble in 2017, and now into 2018.

C.

Re: Too much Daily Mail for my liking

Mate, you're the one obsessing about it. Chill, or maybe seek help?

C.

Re: RobertLongshaft

"More anti trump propaganda"

Except for the parts where we said H-1B pushes down wages and pushes out American workers?

C.

Re: "....get Samba working on HP-UX....."?

"Samba has worked fine (well, as fine as it can) on HP-UX for years!"

Bear in mind this is HPE asking – according to the speaker, HPE (post-HP split) needed help getting Samba working (again).

C.

Re: Re: Long live marketing

SLS is non-commercial (NASA). BFR doesn't exist. This is pretty black and white, ppl.

C.

Re: Dr Marvel's wonder liniment...

>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.

Re: DontFeedTheTrolls

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.

Re: Re: Possible error?

Oops, thanks, fixed. Don't forget to email corrections@theregister.com if you spot anything wrong. We can't read every comment (there's too many) but we can read every email.

C.

Re: danito

Pretty sure the microcode adds an MSR that can control CPU behavior to mitigate the vulnerability (ICBW) and there is exploit code. It's available for Meltdown and Spectre. It's generic.

C.

Re: Not Apples for Apples

I recall a senior Digital Ocean person swearing blind DO doesn't oversubscribe.

C.

Re: israel_hands

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.

Re: Skyfall and Solace vulnerabilities?

Mythic Beasts is just the hosting company. And it's basically bollocks. It's 99% a hoax.

C.

Re: Re: Quality journalism

"Gareth Corfield does then deletes comments to make it look as though he doesn't."

Not taking criticism from a moron who can't string a sentence together.

C.

Re: nick_rampart

No.

C.

Re: It is a serious, fundamental design flaw

Yes, as we've repeatedly reported since January 2, and were the first to report. Read El Reg ;-)

C.

Re: rjed

"QUIC is not been deployed yet because it is still not a standard !! IETF is working on it and has recently pushed back the dates (to end of 2018)"

Yeah, so as we said, only Google seems excited by it. Everyone else seems to be taking their sweet time - of course, they're allowed to do whatever they want. But the point is, only Google seems excited by it, mostly.

C.

Re: Germans make an even bigger mess of naval procurement than Brits?

I think it's probably fair to say it's enough work for us to cover UK and US military goofs, let alone Germany's cock-ups, too... But thanks for the link.

C.

Re: Hate to think El Reg was going PC......

Eh, I dunno. We called it The Fappening in the past, and it just seemed the name had morphed to Celebgate.

And I'm all about a writing style that's like your mate at the local boozer. Just not so sure about playing into the hands of a bunch of 4chan degenerates jerking off over people's stolen private images, so to speak.

C.

Re: RLY!?!

Mate, none of what you said above is cool. If you're delivering stuff to someone, serving them food, any kind of day-to-day thing, taking their phone number and texting them weird flirty stuff is awful. The number was provided for business purposes, not to set up a date.

It's one thing to ask a person for their number in a social setting. It's another to delve into a customer record and pull out a contact detail and pester them.

Now imagine this happening every week - it could be on twitter, uber, just eat, work email. It gets old really quick and it's just creepy and sad. If you want to ask someone out, do it properly.

C.

Re: slang v gospel

"you breeze by his 600 gig"

We were charitably hoping he meant 600 gigabit per second.

C.

Re: An interesting statistic on your box of morning cornflakes

"The racial makeup of Cupertino"

Cupertino is a small city in California that happens to have Apple HQ next to it. People who work at Apple, by and large, don't live in Cupertino. They live all over the Bay Area and the world.

No idea what point you're trying to make, anonymous coward.

C.

Re: Terje

Thanks - I'll tweak the article. Sorry, we were mostly working on chip stuff this week and brains were tired. Don't forget to email corrections@theregister.com if you spot anything wrong. We don't have time to read every comment.

C.

Re: "Isn't making it go mainstream before this date kind of a bad thing?"

We asked Intel what was going on, twice, and had no response - not even a no comment, or an off-the-record explanation. We were certain with what we had - given the LKML discussions and information from other sources - so, why not warn the world that big changes are coming?

We offered no exploit code. Just a heads up that important alterations were being made to crucial bits of software. It's not our job to do companies' PR. We can't read minds.

And these changes were being done in the open, so any bad people paying attention could have known what we knew or more, and started exploiting it.

A lot of vendors hold us at arm's length, hoping we'll go away. We regularly get the silent treatment from various - but not all - companies. We're not going to sit on stories just because we get a no comment/no reply. Turned out this one was quite a big one. We had no idea it would be this big.

C.

Re: Shouldn't we be upset with The Register for broadcasting this?

>apparently against the wishes and advice of everyone involved

No one we contacted for comment told us to stop.

C.

Re: Big John

"The author tried this same shiza a couple weeks ago"

Stop being such a snowflake, dear.

C.