Replies

Oh blah blah blah! Apple loons are the $hit of the tech world. Whether you turn up you sink up the place and then feign suprise when people point out to you how much you stink. This latest load of swordmarker crap is just typical of how utterly myopic and child-like most of you are.

Jeez, take a pill.

Apple has excellent attributes. So does Android. And anyone who believes one or the other is more or less protective of privacy is, IMHO, dreaming. At the very least, requiring the uploading of your fingerprint into an ID database to start the device should give you a clue. As for Microsoft, well, someone had to be at the bottom of every category.

At the very least, requiring the uploading of your fingerprint into an ID database to start the device should give you a clue.

If you had a clue, you would not post such nonsense.

And anyone who believes one or the other is more or less protective of privacy is, IMHO, dreaming. At the very least, requiring the uploading of your fingerprint into an ID database to start the device should give you a clue.

Google and Facebook have been caught with their fingers in the cookie jar much more. The reason is simple. Apple is a hardware/software company that gets people to sheel out $$$ for products. Google and Facebook make their money primarily from advertising and the moetization of information. FWIW, the digitized fingerprint feature is not stored as an image, but as a series of numbers that cannot be used to regenerate the original fingerprint. In any event, you can turn that feature off.

Apple has excellent attributes. So does Android. And anyone who believes one or the other is more or less protective of privacy is, IMHO, dreaming. At the very least, requiring the uploading of your fingerprint into an ID database to start the device should give you a clue. As for Microsoft, well, someone had to be at the bottom of every category.

Talisker, Apple does not, ever, require you to "upload" your fingerprint to start your device. The fingerprint is not even stored on your device. A HASH representation is stored ON your device in a secure storage area on the chip in your device and never sent beyond your device. The hash is store in the "Secure Element" chip in your device. It goes nowhere else. Even if it did, the hash, as is your passcode, is entangled with your devices UUID and only works with it.

Your fingerprint is re-read each time and then a new hash is calculated, entangled with the UUID, and then compared with the stored entangled hash. If it is within parameters, the device is started. If not, it will not be. . . and you are required to use your passcode.

If someone were to be able to get a hold of the entangled hash, they could not reconstruct your fingerprint from it. . . ever.

On the other hand, Samsung's Knox Security DOES keep a photo of your fingerprint, and your passcodes in a clear text file hidden unencrypted in the their Libraries. . . and it can be found. Oops.

So does Android.

Here is the link to the information on Samsung's vaunted Knox Security being compromised:

"Samsung's Knox security layer for Android generates weak encryption keys, stores passwords locally and gives users login hints in a fatal "security by obscurity" design "compromising the security of the product completely," a researcher has detailed."

This was discovered after Samsung's Knox products were certified by the Obama Administration's NSA and the National Institute of Standards and Technology as acceptable for their "security and classified" document phone because of the security of Knox. . . and anyone can easily get into it, anyone. LOL!!!!