Security in 2017 (was "OK, the list *really* needs to be fixed")

Rick Harrison harrison at
Tue Jan 3 17:29:22 EST 2017

Hi Bob,

That is both a great and terrible story!
One really can’t make this type of
story up either because it’s too bizarre.

Sorry to hear that it was a true one for you!
Thanks for sharing...


> On Jan 3, 2017, at 4:16 PM, Bob Sneidar <bobsneidar at> wrote:
> And redundant backups are just one more vector to your data. Really, security has to be balanced with usability. Absolute security is to never write, type, speak  or otherwise store any information you want to protect, or which might give clues to any information you want to protect. This is of course absurd. We sacrifice some degree of confidence for some degree of usability. I personally do not do bit level encryption because of the reason stated below. It's too easy to lose everything. But locking down you information as best you can is always wise. 
> By way of example, I took a phone into Apple where I had the fingerprint recognition enabled. The touch screen was intermittent, so I had them replace the touch screen. They did of course, first have me disable the fingerprint recognition, and turn off Find My iPhone. I got the phone back bricked. They had damaged the cable that goes from the security chip to the logic board, and now the phone was impossible to restore. The chip marries itself to the board, and even replacing the cable would not have solved the problem. Otherwise anyone could bypass the security by simply putting a new security chip/cable in the phone. 
> Yes, too much security is a bad, bad, very bad thing. 
> Bob S

More information about the Use-livecode mailing list