6 ms·
Not any longer. Users must explicitly approve app access to contacts the first time it's requested.
by aaronbrethorst 13y ago
Not any longer. Users must explicitly approve app access to contacts the first time it's requested.
- devx 13y agoYes, and what else we don't know about, thanks to their closed software? Yes, Apple just told us your fingerprint will be stored locally. So? Does that mean Apple si telling the truth, or couldn't leave a backdoor for NSA to get the data? No it doesn't, and we wouldn't know if they did do that. That's the problem with closed software.
- jarcoal 13y agoI'm not going to say that your fingerprints won't fall into the wrong hands, but it's incredibly simple to monitor network traffic from the device, and it's a guarantee someone will do this just to see. It's also a guarantee that Apple knows this, so why bother lying?
- coldtea 13y ago>That's the problem with closed software. That's also the problem with open software people get off of the internet/provider in binary form instead of compiling it themselves. That is, all software.
- scardine 13y agoFor all practical concerns, downloading FOSS in binary form is not that worst compared to source code, unless you are willing to audit thousands of lines of code before compiling (and is competent enough). The exploit can even be hidden into the compiler itself, not in the source. I don't have a solution for this problem, I'm just commenting the fact that it is more complex than "compile from source" and that you have to draw a line somewhere unless you assemble your hardware from raw materials and write your own software.
- brymaster 13y agoAnd that only took them until iOS 6! My point still stands.
- deleted 13y ago[deleted]
- epistasis 13y agoThis is really stretching the point, because it's implying that not only is a single breach proof of complete insecurity, but also that even a temporary breach is proof of complete insecurity. If one is going to reason in black and white, then the only answer is that everything, absolutely everything, is susceptible to being compromised. In such a black and white world, there's no security benefit for open source software, because it is also possible that you could be tricked into running something that compromises your security, as it is also possible to have a design flaw in the architecture of open source code, as it is with closed source code. It is only when one allows the concept of risk that a coherent security picture can emerge. Leave absolutes to mathematical proofs, and trust and risk assessments to the real world, at least until we can prove code correctness for an entire computer system.
- brymaster 13y ago> This is really stretching the point, because it's implying that not only is a single breach proof of complete insecurity, but also that even a temporary breach is proof of complete insecurity. Not stretching the point at all, because this isn't the only case of a security or trust breach, and once that is broken, you have no reason to trust them again. OP's post made the ridiculous claim that somehow Apple's 'controlled' approach protects users. I provided evidence which proved that false.
- halostatue 13y agoTotally stretching the point. Apple had to make stands as to where to trust developers and where not to trust them. Certain developers broke that trust with Apple, and Apple had to regain the trust with users. Blame Path &c., not Apple, for abusing a feature that was originally provided for the convenience of developers and users together.