[Swordmaker]

John McAfee jumps the shark. . . explains on Russian TV how to open the Apple iPhone 5C in just 30 minutes. Only he instead shows his total incompetence. His method is based on his mistaken idea that Apple stores the User's Passcode somewhere on the iPhone, and that a hardware engineer could then "read the memory for the first entry of the Touch Screen" follow the "location to the memory storage location of the user's passcode" and then "READ IT from memory! What part of "Apple does not store the User Passcode on the iPhone" does John McAfee fail to grasp? — PING!

John McAfee Shows his incompetence
in his Apple v. FBI/DOJ case solution
Ping!

The latest Apple/Mac/iOS Pings can be found by searching Keyword "ApplePingList" on FreeRepublic's Search.

If you want on or off the Mac Ping List, Freepmail me

[Swordmaker]

I would certainly like to meet these miracle workers, the hardware engineer and software engineer, who can take apart an iPhone 5C, and remove 16GB of data and OS and apps, and then disassemble them all, find the OS components inside all of that, find it in approximately 1 BILLION bytes of code, locate the proper memory location in the iPhone, then read the proper 1s and 0s out and interpret them into the correct passcode. . .

All in 30 minutes.

Truly miracle workers.

Of course, there's the other problem, Apple doesn't ever store the passcode anywhere on the iPhone, only a one-way HASH representing that passcode with which a newly input and re-calculated HASH will be compared every time a user inputs his passcode to open his or her iPhone, so there IS NO STORED PASSCODE to locate.

Next, even were these miracle workers able to find the HASH, it's a one-way calculation. It is impossible to start with the HASH and, even if you have the algorithm that created it, to work it backwards, arrive at the seed value, the User's passcode, from which it was created.

Finally, that HASH is stored in an EPROM like area inside the iPhone 5C's A6 processor called the Encryption Engine, a sub-processor area, which can only be written from without but not read from outside the Encryption Engine by the A6's normal processing of Apps, or by any external hardware probing such as a JTAG probe. Anything inside the Encryption Engine, is for all extents and purposes, walled off, invisible to apps and hardware probes because it cannot be read from outside the Encryption Engine and only the RESULTS of what is done with those data can be released from within that Engine.

John McAfee's opening scheme simply cannot work.

[Read Write Repeat]

I can’t trust a man who tans unevenly.

[Yo-Yo]

What part of "Apple does not store the User Passcode on the iPhone" does John McAfee fail to grasp? — PING!

McAffe is a McAss, and uncompiling code does not allow you to easily "read" the program, not like having the original source code does.

But of course the iPhone stores the passcode on the iPhone. If it didn't you couldn't unlock your phone while it was in "airplane" mode where the wifi and cellular data transmitters are turned off. But it is stored as an encrypted number, and cannot be decrypted without knowing the original number.

[Protect the Bill of Rights]

Since I do not understand anything beyond “you need a hardware engineer and a software engineer, “ my reply to McAfee is either do it or get off the pot. Quit talking about it. Get a 5c with iOS 9 on it, have someone lock it and show the world how smart he is [or not].

[Cyberman]

Don't laugh -- you're next!

[dayglored]

LOL. John McAfee should be read for entertainment purposes only.

He can't be taken seriously.