Re: Tom 64
Thanks for deliberately misreading the story. Post less.
C.
3533 publicly visible posts • joined 21 Sep 2011
Open the Terminal app (in Applications->Other) to get a command prompt. Use the ls command to list info about the files, eg type:
ls /tmp/Updater.app/
Or rather type 'ls ' and then cut'n'paste the file name. Hit enter, and you should see:
ls: /tmp/Updater.app/: No such file or directory
Which means the directory doesn't exist so you're OK. Repeat this for the other files listed. You can quit Terminal when you're done.
C.
If you apply your patches, you'll be OK. If you're using Windows or iOS, you're pretty much immune anyway. There isn't a tool to check as far as we're aware. If you're using a recent Linux or Android 6+ or macOS or openBSD or an IoT gadget that uses Linux, you're at risk.
But bear in mind no exploit code attacking the flaw is out there, someone has to be in range, and it's right now tricky to do. Grab the latest security updates for your devices so that you're protected in future.
C.
"It is true, however, that there hasn't been the kind of well-informed, detailed explanation of the vulnerability that The Register would normally do."
The flaw is fairly complex but well-explained in the paper, which is public. We've linked to it in previous coverage. You should read it if you're interested in nonces and key installation. If you're aware of WPA2's cryptography, it's an easy read.
Instead, we've focused on the impact - that's what matters most.
C.
Microsoft is giving up on smartphones, but loves the idea of ARM-powered laptops running Windows 10. Microsoft and Intel had a major falling out over PC processor prices, so Redmond turned to a CPU supplier dying to break out of mobile: Qualcomm.
So forget Microsoft in your pocket. Microsoft wants to be on your lap or desktop, with Windows 10, on Qualcomm ARM, or Intel or AMD x86.
C.
Great question, Steve. We cover outages when we can. Some outages are more important than others (ISPs and multi-tenant cloud services, especially) so we jump on those. Facebook going down for a few minutes, not so much. Sometimes we're all working on other stories, and by the time we drop everything, and start writing up the outage, the thing comes back online.
The Verge is about as techie as a bent paperclip. It's a marketing vehicle for Silicon Valley.
C.
I'll let you in on a little secret: we don't really care if the scansion doesn't quite match up - worrying about a syllable here or there, life's too short for that.
In this case, we couldn't fit the 'the' in because then the headline would not fit in its little space on the front page, break over many many lines and just look ugly. And I'd rather have a tidy looking headline than one that fits the 14 syllables perfectly.
Sorry, not sorry. But thanks for appreciating the headline. We couldn't write one anywhere else in the enterprise IT news world.
C.
"This a another faux-outrage created by non-Apple users, as usual."
Apple is being super confusing here.
"In iOS 11 and later, when you toggle the Wi-Fi or Bluetooth buttons in Control Center, your device will immediately disconnect from Wi-Fi and Bluetooth accessories. Both Wi-Fi and Bluetooth will continue to be available"
Will both continue to be available even though disconnected. Huh? Turns out you have to go to the *settings* page:
"To turn off Wi-Fi, go to Settings > Wi-Fi and turn off Wi-Fi.
To turn off Bluetooth, go to Settings > Bluetooth and turn off Bluetooth."
You can see why it's irritating people. Off should always be off, not nearly off until you find the other lever to pull.
C.
Hate to 'actually' you, but ACTUALLY: Our revenue this year is neatly following 2016's record high. As in, 2016 smashed El Reg's all-time ad sales records. The unsung heroes here are our sterling ad sales team, and us news scribes are in their debt.
So yes, we sometimes run vendor-sponsored articles - clearly labelled sponsored or promos - and they make us a decent amount of money. Take 'em as you like: they are written by freelance journos we vet for quality. And the pieces are super interesting. Don't skip over them just because they are biz-sponsored. It's all part of the El Reg mix.
However, a vast chunk of our cash comes from display ads against our top news articles - which are produced well away from any vendor interference.
We strive to provide highly technical and accurate IT news and features independently and ethically.
Ultimately, this all funds the snark, sarcasm, the exclusives, the analyses, the features of The Reg that you love and we'll continue to serve.
Hey Andrew - it's Chris from Drobe. Remember those RISC OS days? Ah yeah. Now I'm at El Reg. Lol!?
Anyway. Thanks for reminding ppl about the extended iOS settings to actually switch off radio comms. We linked to Apple's instructions, so no foul there.
"The continued race to the bottom in El Reg persists"
The fact that we're the most read in the enterprise IT space, and that we're making year-upon-year growth in ad revenue and profit, suggests you're full of shit, Andrew.
C.
This article isn't written for people who have avoided the bug. It's written for people hit by the bug who want to know WTF is going on. And check the link - Apple admits there is a problem.
Also, ppl saying their gear works - are you using the Outlook app? That app is crippled: check out the reviews for it. The UI is mashed beyond repair. That's not a great UX for ppl.
There's no sensationalism going on here. iOS 11 doesn't fully work with Microsoft's software - Apple says as much. If it works for you, great. Judging by the stats on this article, millions disagree that all is ok.
C.
"ranting about the SJWs is poor form"
Ah, come on. Our job is to summarize as best we can complex stuff. In between the usual in-fighting and politics that rage in some open-source projects, the thing for us that stuck out was the CoC side, and so that's the focus here. To us, it's the straw that broke the camel's back.
The ability, or inability, for Node.js to self-govern properly as a FOSS project is best left to another story, and something we can look into. In fact, it should be obvious that, after two splits now, that all is not well in the project.
It's our job as journalists to identify the information that is most interesting to readers. And in our view, a bitter argument over CoCs - which is a rather large policy issue these days in tech - is more significant than people flaming each other on mailing lists.
C.
"the EPO has got nothing to do with the UPC"
Apart from granting them – and, for years, spent a lot of time, money and effort promoting UPC, is a huge cheerleader and advocate of UPC, and stands to gain a lot from the UPC coming into force.
So yeah, nothing to do with UPC, lol.
C.
Couple of observations, my dear fellow:
1. Your comment pointed out a typo in the article. Our standard operating procedure when we see corrections in comments is to fix the typo and reject the comment - because the comment is unlikely to make any sense after the tweak is made. You should email corrections@theregister.co.uk so problems can be addressed ASAP. We don't have time to read every comment but we do like to correct all errors.
2. You need to, as we say in California, chill out.
C.
"I'm not saying it'd be fast or efficient"
Well, bingo. It's hard because it's virtually impossible to calculate using today's systems. And your numbers are off. Read the full problem:
"The total number of ways of choosing one hundred students from the four hundred applicants is greater than the number of atoms in the known universe! Thus no future civilization could ever hope to build a supercomputer capable of solving the problem by brute force; that is, by checking every possible combination of 100 students."
C.
I almost rejected this comment, but I approved it so I could point out its idiocy.
"It's been appropriated by straight-out low-IQ and hysterical thought enforcers and politicians out for a quick rallying so much that it's become meaningless."
MATE, THEY ARE WEARING FUCKING NAZI SWASTIKAS. FUCKING NAZI SWASTIKAS. THEY ARE FUCKING NAZIS. No, this isn't name calling or shock labelling by the left.
THEY ARE WEARING FUCKING NAZI SWASTIKAS. IN AMERICA. IN 2017.
C.
"What browsers is this applicable to?"
If you follow the link in the story (and read the sentence) it was reported by a Brave browser developer because it affects Brave. Brave is based on Chromium, so it may apply to both. How Wireshark and Charles Proxy are detected is under investigation – it's looking like RPC via JavaScript so may be cross platform.
C.
"It would be *so* nice if we could have an honest debate about what the guy *actually* wrote"
He wrote a 3,000-word ramble. You gotta forgive people for summarizing it - and for a lot of people, it was a rather long-winded way of saying: it's ok to assume people are genetically incapable of some jobs. And that's rather in the face of efforts to ensure a fair and diverse workforce.
C.
"What does the part about maths have to do with the memo?"
Ah, so tedious. It was an example of how there are sod all differences between men and women if you're not interested in things like physical strength. You're still missing the point, the contradiction within the memo. You can't on one hand scream about considering people purely on merit, and then on the other hand bang on about how some people are incapable of tasks due to their biology.
Which is it: giving everyone a fair crack to prove themselves, or writing off whole chunks of the population? It's stupid.
As for the silencing of debate - if your daft ideas and reasoning can't stand up to scrutiny then that's really your headache. I don't like to see people pushed out or moderates turned into extremists, but honestly. Calm down. It's just a stupid ill-thought-out memo that got someone fired.
C.