Linked by Thom Holwerda on Mon 1st Apr 2013 12:25 UTC
Apple "Last Friday, The Verge revealed the existence of a dead-simple URL-based hack that allowed anyone to reset your Apple ID password with just your email address and date of birth. Apple quickly shut down the site and closed the security hole before bringing it back online. The conventional wisdom is that this was a run-of-the-mill software security issue. [...] It isn't. It's a troubling symptom that suggests Apple's self-admittedly bumpy transition from a maker of beautiful devices to a fully-fledged cloud services provider still isn't going smoothly. Meanwhile, your Apple ID password has come a long way from the short string of characters you tap to update apps on your iPhone. It now offers access to Apple's entire ecosystem of devices, stores, software, and services."
Thread beginning with comment 557291
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: it happens to everyone
by Soulbender on Tue 2nd Apr 2013 02:32 UTC in reply to "it happens to everyone"
Soulbender
Member since:
2005-08-18

it's in a inescapable part of a rapid/agile software development process.


If security flaws are an "inescapable part" of your development process then your process is fundamentally flawed.

They run automated security tests and when those tests don't cover a particular case a security lapse occurs.


If the software was properly engineered that wouldn't automatically happen.

Although this exploit was 'dead simple' it was also not at all 'obvious' as it was not previously discovered.


The fact that it wasn't discovered before doesn't mean it's not obvious.

Reply Parent Score: 3

RE[2]: it happens to everyone
by Nelson on Tue 2nd Apr 2013 03:49 in reply to "RE: it happens to everyone"
Nelson Member since:
2005-11-29


If security flaws are an "inescapable part" of your development process then your process is fundamentally flawed.


I don't think so, it comes with the territory -- people make mistakes. Though I disagree with the OP's argument that agile is more prone to security flaws.

Its also worth noting that Apple's particular flaws, while still flaws and while they are still just a normal part of the process, are especially basic. Security is a mindset that's built into the culture of a company. If Apple is making these kind of mistakes, there's something wrong there.

Reply Parent Score: 2

Soulbender Member since:
2005-08-18

I don't think so, it comes with the territory -- people make mistakes.


Of course, that's unavoidable but the argument was that security issues was inherent to the process Apple use to develop software. If that's the case the process is flawed.

Reply Parent Score: 2

RE[2]: it happens to everyone
by Alfman on Tue 2nd Apr 2013 03:54 in reply to "RE: it happens to everyone"
Alfman Member since:
2011-01-28

Soulbender,

"If security flaws are an 'inescapable part' of your development process then your process is fundamentally flawed."

I agree with you, it's shameful that there are developers who regularly produce security holes in software. But at the same time it's sort of a biproduct of the fast and cheap development process that companies are seeking. My experience with most companies is that "security" is little more than a PR selling point and not a genuine development philosophy.


"If the software was properly engineered that wouldn't automatically happen."

I think the OP was merely explaining the situation on the ground rather than trying to justify it. If so, I think he's right. It'd be nice if things were engineered correctly in the first place, but security is rarely a priority in development and usually only gets tackled in hindsight. I agree with you it's the wrong way to do it.

Reply Parent Score: 3

RE[3]: it happens to everyone
by Brendan on Tue 2nd Apr 2013 05:07 in reply to "RE[2]: it happens to everyone"
Brendan Member since:
2005-11-16

Hi,

I think the OP was merely explaining the situation on the ground rather than trying to justify it. If so, I think he's right. It'd be nice if things were engineered correctly in the first place, but security is rarely a priority in development and usually only gets tackled in hindsight. I agree with you it's the wrong way to do it.


A company's only goal is profit - their products are just a by-product of that. If engineering things correctly costs more than the potential cost of fixing things if/when they break; then engineering things correctly is the "wrong" way to do it.

- Brendan

Reply Parent Score: 3