{"id":1142,"date":"2009-09-14T15:57:44","date_gmt":"2009-09-14T14:57:44","guid":{"rendered":"http:\/\/blog.intego.com\/?p=1142"},"modified":"2026-07-01T11:13:21","modified_gmt":"2026-07-01T18:13:21","slug":"response-from-apple-regarding-iphone-anti-phishing-problem","status":"publish","type":"post","link":"https:\/\/www.intego.com\/mac-security-blog\/response-from-apple-regarding-iphone-anti-phishing-problem\/","title":{"rendered":"Response from Apple Regarding iPhone Anti-Phishing Problem"},"content":{"rendered":"

We reported last week that Apple had added an anti-phishing feature to the iPhone OS<\/a>, but that this feature did not work consistently. It turns out that the feature, while in the operating system, was not “primed”. Apple has responded to this issue in an article on The Loop<\/a>, saying that users needed to perform an operation to get it to work. An Apple representative is quoted saying the following:<\/p>\n

After updating to iPhone OS 3.1 the user should launch Safari, connect to a Wi-Fi network and charge their iPhone with the screen off. For most users this process should happen automatically when they charge their phone.<\/p><\/blockquote>\n

Now, this is interesting. How are users to know that they have to do this? Nothing on the iPhone tells them to do so, and it is likely that many users never turn on wifi on their iPhones. Apple should have provided an initial database with the iPhone OS update, or should have given clear instructions to users. This is a very lax way of providing a security feature.<\/p>\n

We see a number of problems: <\/p>\n