Skip to main content

iOS security vulnerability

My post earlier today about hacking the iPhone 5S's TouchID was talking about something major: access to everything in the phone. But that post mattered to you only if you have an iPhone 5S (the brand new, higher-end model). There is another vulnerability that affects just about everybody with an iPhone, at least if you've upgraded to iOS 7.

If the phone you're trying to get allows access to the Control Center from the lock screen, it's possible for someone who knows a fairly simple trick to get into your photos and some other parts of your phone's content. You can read about it here:

Forbes/Andy Greenburg: 
iOS 7 Bug Lets Anyone Bypass iPhone's Lockscreen To Hijack Photos, Email, Or Twitter

I just confirmed that this is possible using my own iPhone 5. I'm writing this on 9/23/13 and using the current (latest) version of iOS 7 (11A465).

Unauthorized access to your email is the biggest danger here. Remember, somebody with access to your email may be able to change your password to other accounts. So even though this bug doesn't immediately give the intruder full access to your phone, it's potentially serious.

But there's a fix, and you should take advantage of it. Simply disable Control Center on the lock screen:

Settings > Control Center > Access on Lock Screen (turn off)

Should be off by default but it isn't.

Comments

Popular posts from this blog

Virtual List Basics

The conceptThe basic trick behind virtual lists is the wonderful GetValue() function. GetValue() takes two parameters: A list of return-delimited values A number specifying which value in the list to get

For example say you have a field in a single record called “List of Values” and it contains the following:

   Apple
   Boy
   Cat
   Doorknob
   Elephant
   Fish
When that record is selected, GetValue ( MYTABLE::List of Values ; 4 ) will return “Doorknob”.

The brilliant idea is to replace the list of values stored in a field with a list in a global variable.

The basic implementation, part oneCreate a table called VIRTUALLIST. In it, define these two fields: VALUE NUMBER: a number field Value_calc: calc field returning text value, = “GetValue ( $$VALUES; VALUENUMBER )”. Make sure that this value is an unstored calculation.

Go to the layout for the VIRTUALLIST table and create some records. Later you can create hundreds or thousands, but right now just ten will do. Use ReplaceFieldContents to po…

Setting up OAUTH with Google in FileMaker 16

Setting up OAuth with Google in FileMaker 16Posted by William Porter Intended audience: Intermediate to Advanced FileMaker developers Date of publication: 2017-June-06
One of the many exciting features in FileMaker 16 (released last month) is OAuth or Open Authentication. Open Authentication allows users to connect to a FileMaker database after authenticating with an external (non-FileMaker) account. At the present time, FileMaker supports OAuth through Google, Amazon and Microsoft.
If you're a developer there are two main questions to answer. First, should I do this? And second, how do I do it? I'll answer the first question later. It's important.
But the other question--How do I setup OAuth?--is answered in the attached document. I wrote this tutorial with the help of my friend and colleague Taylor Sharpe of Taylor Made Services, also here in Dallas. We provide step-by-step instructions on how to get your users authenticating into your FileMaker databases using Google. (A…

Getting out of fullscreen mode in FileMaker Pro

In version 2 of Acquittal, our criminal defense case management app, we're doing some nifty stuff with windows, and that means we're finding out that even in FileMaker Pro 15, we still don't have quite all the tools we'd like for managing windows.  One problem is how to trap for the possibility that the user has switched into fullscreen mode. The other problem is how to get out of it.


Is this window in fullscreen mode?
This one's not too hard. This calc formula seems to do the trick:

Get ( WindowHeight ) = Get ( ScreenHeight ) and
Get ( WindowWidth ) = Get ( ScreenWidth)

That will return true if the window is in fullscreen mode, false if it's not.

Why does this matter? Because there are certain things that you can't do with a window if it's in fullscreen mode. In Acquittal, for example, there are times when we want to generate a second "sidecar" window, then display the main and sidecar windows side-by-side. Can't do it if the main window …