Xtra News Community 2
April 16, 2024, 08:00:09 pm
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Welcome to Xtra News Community 2 — please also join our XNC2-BACKUP-GROUP.
 
  Home Help Arcade Gallery Links BITEBACK! XNC2-BACKUP-GROUP Staff List Login Register  

The FBI vs Apple Corp.

Pages: [1]   Go Down
  Print  
Author Topic: The FBI vs Apple Corp.  (Read 1441 times)
0 Members and 1 Guest are viewing this topic.
Kiwithrottlejockey
Admin Staff
XNC2 GOD
*
Posts: 32247


Having fun in the hills!


« on: November 09, 2017, 12:49:41 pm »


This is how encryption works with the latest iPhones…


The encryption key is constructed by the iOS Encryption Engine processor and is composed of FOUR elements, only one of which is related to the user's passcode.

1. The DID: a Device ID: This ID is the same for all devices the IC is installed in and is burned to the Secure Enclave IC when it is made.

2. The UUID: a Universally Unique ID, an identifying code made up of unique characters assigned randomly at the time the Secure Enclave memory integrated Circuit is first burned in the silicon. No record of this ID is ever kept at the IC maker or anywhere.

3. A truly random number generated from environmental sensors such as the device's cameras, microphones, position sensors, and gps, when the user first inputs or bypasses inputing his AppleID. This too is stored in the Secure Enclave.

4. The One-Way Hash of the user's passcode (or a default number used when a user elects to not enter a passcode). This, too is stored in the Secure Enclave. Note that the user's passcode can be anything from a four to six digit number all the way to a 256 character password, which can use all 223 characters that are available on the virtual iOS keyboard. I would not recommend trying to remember a passcode of that length. LOL! However, you could if you wanted.

An algorithm, also stored on the Secure Enclave, is used to entangle the user's passcode into the concatenated UUID, DID, and Random Number (these three total 128 characters before the user's passcode Hash is entangled). In any case, the actual key is padded by the algorithm to at least 144 characters in length to do the encryption decryption EACH TIME THE USER INPUTS A CORRECT PASSCODE, although it can be longer when the user's passcode is entangled.
 
Bottom line, Apple doesn't have the ability to crack it because THEY DON'T WANT IT. They're safer from demands from the Feds that way.

Report Spam   Logged

If you aren't living life on the edge, you're taking up too much space! 

Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by EzPortal
Open XNC2 Smileys
Bookmark this site! | Upgrade This Forum
SMF For Free - Create your own Forum


Powered by SMF | SMF © 2016, Simple Machines
Privacy Policy
Page created in 0.055 seconds with 17 queries.