Re: Must be a component issue.
"It's an extremely difficult and complicated subject and Tim Cook can no longer give all his attention to it, as he has other jobs."
One of those ought to have been succession planning for his previous job.
42029 publicly visible posts • joined 16 Jun 2014
"you normally no longer look inside the component."
But as you then go on to say it might be a good idea to check. It's the job of QA to keep a tight reign on the quality of components being used. It can't be an easy job if your company doesn't assemble the final product nor, I suppose do Apple route all supplies to the assemblers via themselves. The umpteen things that can go wrong in such a situation mean that they really need to put the effort into managing their supply chain.
"I suspect the batteries may come from an outfit that delivered good batteries when they were asked to supply a small number for development and QA, but immediately started cutting corners once they had the big order in."
You may well be right but wasn't Tim Cook supposed to have been a supply chain specialist before he was elevated? This is the sort of thing such a specialist should be in control of.
"I sometimes wonder if a really secure system will appear, written from the ground up"
From the ground up would be essential. Then there's the question of putting convenience secondary to security. It would be a hard sell without a few major disasters to existing OSs to help it on its way. It would also be a good idea to think in terms of a pair of complementary systems for client and server functions so that neither carries unwanted baggage from the other.
From Wikipedia:"Julie Larson-Green (born 1962) is the Chief Experience Officer (CXO) of the Office Experience Organization at Microsoft,[1] where she has worked since 1993."
"Experience" is one of those warning words. Finding it twice in the same, introductory sentence simply underwrites just how bad things she can make things.
Having said that I've recently been looking at KDE 5. It's almost as bad with endless widget styles with the same flat button look and themes with squiggles for icons. With any look the nadir may be reached if someone introduces a Big Jules theme leaving all the buttons and icons blank* and then things can start improving.
*PCLinuxOS has almost achieved this, the default window buttons are simply coloured spots which only display an icon on mouse-over.
"Upgrades are not always improvements."
Quite so. That's a good reason to stick with LTS systems as far as possible. It reduces the number of occasions you have to spend time chasing after someone's failure to maintain backwards compatibility. Bleeding edge distros are fine if you want to play with them. If you want to get stuff done use an LTS for as long as possible.
"This gets really, really bad when you consider that a lot of distros keep the kernel version stable and just backport security fixes."
If I use version N of the kernel because it supports my hardware and has the features I need why would I want more than security update providing those come at regular intervals? I'm old enough to remember that upgrades all to often means breakage and have no intention of having to keep fixing things because someone somewhere couldn't be arsed to pay attention to backward compatibility. That's why I like Long Term Support versions.
So here's Debian 7, not at LTS (staying pre-systemd) and the current version is Debian 9 (equivalent to 10 in Microsoft numbering ;). What's the kernel number and what's the date the last version arrived? 3.2 and just over 2 weeks ago on 20th of September.
"They have over 2 decades worth of experiences of dodging that one. That's why they have these exabyte-sized conditions you have to agree to."
Whether these EULAs are worth the paper they're not written on depends on your jurisdiction and status (consumer vs professional).
Try to remember, this Khosla dude will be just as upset at a lone jogger on "his" beach at sunset as he would a major twelve-dozen keg barn burner with The Who's sound system cranking multi-genre, multi-decade rock&roll for three days
Not saying you're wrong but it sounds like a statement that could be tested.
surely it would of become very obvious once the robot went to retrieve the tape from the drive, and failed because 'I can't find the tape!'
The article describes exactly this except that the tapes were missed on the shelves and didn't get as far as the drives.
Even tapes that the team put on shelves by hand weren't being detected.
“The robot sometimes even tried to place other tapes in those 'empty' slots,”
I complained to "bitdefender" because with their new enforced fucking "cloud" system, not only can they "snag" files. (never used to happen with the standalone version, which they discontinued)
I believe Bitdefender are a UK company. Assuming you're also in the UK invoke your rights under the DPA or, better still, wait till next June & hit them with the new, GPDR-enabled Act. And in the meantime, don't use them. "Cloud" should have been a warning to stop right there.
"For the thousandth time, counting CVEs does not indicate relative security levels."
Doug, there's no point in trying to explain things to A/Cs spouting the MS party line. They're only doing what they're told. You don't expect them to actually understand any of it do you?
"the very probable fact that, spook or no, management will be using Windows and management wants their time sheets, planning, expense reports etc done on time. I haven't heard of a lot of Linux versions of the products that handle that, so you'll be most likely using Windows for all that stuff."
Management should be using what the organisation's security bods specify which, you'd hope, would be something more like Open BSD. LibreOffice will run quite nicely on BSDs so I can't see any problems with the sorts of management stuff you mention.
"t'll probably cost less to deal with the fallout than to actually do things right."
Pay and cost, at least monetary cost, are two different things. It may cost the vendor money to do things right but if they don't you may pay - with your life.
Of course, there's always the other aspect of it: if the market is properly regulated you, as a vendor, don't get to sell your product if you're not doing things right so you don't get any money at all. And as it's the same for your competitors you're not at a disadvantage by doing things right. The only way to disadvantage yourself would be not to spend the money in the first place.
"It would be possible for someone to have their personal credit card details accessible on a company PC for booking hotels etc on company business."
That's one category of information I don't have to keep on a PC. It lives in my wallet.
If, however, there's stuff that I think should be kept private it can go into something like Keepass. Even if the disk is encrypted on a company laptop having a separate encrypted file to which the company has no access would have solved the problem. It would also solve the problem of the company backing up the laptop onto their own servers.