Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
Compare cell phone plans using Wirefly's innovative plan comparison tool ×

Comment Re: this kind of thing is usually a DDoS (Score 4, Interesting) 91

While Apple isn't obligated to state while something was does, there are reasons other than a DDoS that seem more likely.

One is that various Apple services use both Amazon S3 and Microsoft Azure for file storage. Given that not every Apple service was down for everyone, it's possible the Amazon outage was related to the Apple outage.

Secondly, numerous other services on the internets were down, including numerous .gov websites belonging to states (,, it's possible a regional Internet backbone was having issues.

Although the most likely reason remains Apple that was working on some backend changes for new features and/or services they'll be announcing at WWDC and something went wrong.

Comment Re: Hmm.... (Score 4, Interesting) 81

A clean install may not work. There is a hook in Windows 8 and later that allows OEM firmware to supply a list of software to install after a clean install.

The feature was originally designed so Windows could automatically install necessary OEM-specific drivers without requiring a custom installer be used. Sadly, OEMs have used it to install vulnerable crapware.

You just can't win against crapware.

Comment Re: i've been there.... (Score 3, Informative) 214

itunes asked if she'd like to sync with the new device. she said yes. it deleted all of the music on her computer, including physical files

This did not occur. iTunes does not permit an iOS device to become the "master device" for songs. It will only copy songs to the iOS device (except for purchased songs, which it copies to the existing iTunes library). It's actually a very common complaint that iTunes won't copy all songs off an iOS device.

Comment Re: Seriously incompetent (Score 2) 214

And that's exactly what Apple will be doing. Since Apple cannot reproduce the issue, and has no real idea if it ever occurs, is a user error, or is a bug, they basically have one option:

Go through all the code that uses FSDeleteObject(), FSUnlinkObject(), and unlink() (The function calls iTunes actually makes) and either replace them with calls to FSMoveObject() or fortify the code with additional error checking they can't confirm will help.

The issue is, under no circumstances is iTunes supposed to delete music files. Even when explicitly telling iTunes to delete files, the code uses FSFindFolder() and FSMoveObject() to move the files to the trash instead of outright deleting it. And for huge collections of files, like with 122GB, deleting items from the trash is not fast since Mac OS X uses assloads of error checking and notification sending to make sure none of the files are in use or lack the appropriate permissions (it doesn't simply unlink() files). This means the user will see a trash dialog counting up and then down the number of files to delete.

Even if there is a rare deletion bug, it's extremely likely most of the reports of iTunes deleting music are false. Even when songs "disappear from the iTunes library" (like if you modify a playlist on one device and have playlist syncing on through iTunes in the Cloud, iTunes Match, or Apple Music), the song files remain on disk.

Comment Re: Who cares? (Score 1) 110

iOS has an anti-replay counter to prevent reimaging like the type you suggest to assist with a brute force attack. Furthermore, the "secure enclave" is a marketing term Apple uses to group disparate security features under one umbrella. Most of the security features under the "secure enclave" umbrella still existed on previous iOS devices.

Finally, the Apple A6 SoC does have its own rewritable NVRAM that can be used to store the number of incorrect attempts without needing to store it on the NAND.

Comment Re: Who cares? (Score 1) 110

You haven't "wrecked" anything. All you've done is proven your unwillingness to learn.

At least you're finally acknowledging it's no where near as simple as brute forcing a 4 digit PIN, as your previous posts claimed repeatedly.

Now you've realized/learned there are other major, significant hurdles to doing a brute force attack, such as finding security holes in other parts of iOS that first allow you to run arbitrary code on the iOS device when you have physical access or getting access to the UID by physically decapping the SoC.

So I assume this means you've stopped claiming it's as simple as reading the NAND directly.

Comment Re: This has reached the point of ridiculousness (Score 1) 110

The core functionality of the encryption methods haven't changed much, as you can clearly see if you compare the iOS 7, Feb 2014 security paper to the 2015 iOS 9 security paper.

There are many excellent guides on how iOS encryption works. There's no need for you to remain this ignorant about how iOS encryption works.

Slashdot Top Deals

If in any problem you find yourself doing an immense amount of work, the answer can be obtained by simple inspection.