Re: 1980s_coder
Yes - now made it clear in the story.
PS: Don't forget to email corrections@theregister.co.uk if you spot anything odd in a story - we can fix it immediately.
C.
3495 publicly visible posts • joined 21 Sep 2011
"I... um... what? This headline is just terribly confusing."
Oi, that's our business model. Confuse the crap out of the reader into clicking on it to find out wtf is gong on.
eg: Rap for rap chap in crap rap app flap
C.
"you grab the most provocative photo of a lady in her pants"
As others have pointed out, it's Paris Hilton. The Reg has had a long-running relationship with the hotel heiress. We named our space-plane after her, put it in space, and broke a world record. She's a trope.
Working in the tech press, let alone the IT world, I've seen sexism first hand, and it's awful. I've seen PRs think it's a good idea to take women journalists out shopping rather than give them interviews. I've seen execs shut women out of conversations at the bar. I've seen inappropriate touching at dinner.
Running Paris Hilton through an AI algo isn't even close to it.
C.
Good grief; not everything has to come from a press release. In fact, we hate taking stuff from press releases. This was sourced from well-placed people familiar with Intel's plans, speaking on condition of anonymity to The Register. Y'know, journalism. Finding stuff out, reporting it, not waiting for the emailed press release.
C.
It's right there on visualstudio.com.
(edit: code.visualstudio.com seems broken now; was working earlier. visualstudio.com works fine. Weird.)
C.
"Of course, the kernel can stop the Device Guard VM and replace it with another."
No, that's not possible according to Microsoft's design. Read the article again, please, I think you missed an important point.
There's an always-on hypervisor, which runs under the kernel and Device Guard. Device Guard is allocated its 'secured' corner, the kernel gets the rest. The kernel controls the vast majority of the machine as a result, but the barrier between the kernel and Device Guard isn't controlled by the kernel. That separation is enforced by the hypervisor.
I didn't want to bog down the story with an OS development 101 class, so I kept it simple. But I think it's all clear if you read it through.
This is all in theory: as linked to in the article, previous secure execution environments on other platforms have been popped by bugs in the interface between the two sandboxes.
C.
Sorry for any confusion: when we say search traffic, we mean people searching for things like "hp notebooks", and Google pushing news articles about HP netbooks to the top of the results. People click on those, and that's your traffic.
For example, if you Google search right now for "Nvidia's GTX 900" the top hit is The Register's article on the open-source Nvidia Linux driver faff. If you search for "Miliband Cameron poll" you may get a Guardian article about the UK election campaign. That's search traffic. A stupid number of people use Google so getting even a tiny slice of that each month is valuable to publishers.
Ultimately, it's about ads. You could shift 50 million page views a month but if you can't extract any ad impression cash from that then you're just another VC-funded blog burning through money.
C.
BryceP gets it. We're rude about everyone. And Google has given the foundation a million dollars here or there. Small beans for Google, but a big chunk for the EFF.
And I'm speaking as someone who thinks the EFF mostly does good. But giving people a shoeing is why we're here.
C.
"It's unacceptable, ElReg!!! Comments now are being censored?"
It's absolutely acceptable. Our house, our rules. We see nothing wrong with curating comments that appear under our articles.
You're always welcome to email our writers if you feel your opinion isn't being heard.
C.
Changed the headline to make it slightly shorter (for design reasons, layout nerds; it now fits in just two decks in the article view). I'm pretty sure your omnipotent deity can cope with an enterprise tech newspaper using his son's name flippantly.
C.
"Not sure where the AES128 comes in."
I believe the app makers are saying AES128 is used for messages, contacts, call logs and other things are encrypted using AES with a 128-bit key. But in the hacker's test, a simple PNG file was 'encrypted' using a single byte 'key' and plain XOR. And only the first 128 bytes of the PNG. Bizarre. So maybe images aren't encrypted in any meaningful way?
I've tweaked the story here and there to make it a bit more clearer.
C.
Thanks for the corrections. I've been through these with the writer and a second source, and made tweaks. Not every change you've suggested has been made, mainly because they're outside the scope of this intro to cabling, but I hope all the factual problems have been fixed up. Let me know if not.
It's worth pointing out the problems caused by a misplaced 'the' changing the meaning of a sentence:
"Unlike the other Ethernet standards, 10GbE provides the only full-duplex, point-to-point links for connecting network switches"
v
"Unlike the other Ethernet standards, 10GbE provides only full-duplex, point-to-point links for connecting network switches"
C.
Very smooth. I mean external buses, or separate interconnects between on-die components. There will always be some kind of bus between the RAM and whatever is reading from or writing to the RAM, but the HSA people want to do this with one cache-coherent bus and one portable programming model.
One thing springs to mind is bandwidth: jamming everything on the same interconnect may be a problem, so I'll look into that. The specification allows you to break up the physical memory into pools if you really want to, as long as you stick to the standardized programming model.
C.
"Even though the title says Austrailians... this applies the world over."
This article was written for our Australian/APAC audience in mind, but I felt it was worth extending to our wider readership so I opened it up to everyone to see.
For context, Australia's leaders are considering retaining people's communications metadata.
C.
Fair points. But, and playing devil's advocate here, what's the difference, really? Whether it's discrete, SiP or SoC, it still looks the same to software, even low-level code.
I meant to put in the article (and TPM on our sister site The Platform mentions it) that it's not truly a SoC (like a bunch of ARM cores with an LCD controller and USB and power management glued alongside in a single package) but I forgot, probably because it's not that important.
I just don't think it really matters, personally, but I'll add a tweak to this story anyway. I just worry this affair has a whiff of holy war about it.
C.