iphone_30_aim_push_notification_accept

Crunchgear is reporting that Till Schadde of Equinux has been noticing some weirdness with his AIM app and push notifications. Namely, Schadde has been seeing his AIM messages go to random recipients. He discovered this by being notified that a message he had sent to his iPhone version of AIM was redirected to a random stranger. That stranger then contacted Schaddle to let him know and to supply him with a screen shot of his message.

In the past, TiPb has speculated that there are indeed some issues with hacktivated iPhones. And for those of you who are unfamiliar with "hackivation", it's simply a process that tricks an iPhone into believing it has authorized itself with Apple via iTunes and is ready to be used, but is actually activated by other, non-Apple software.

These hacktivated iPhones are not being assigned a unique push ID by Apple the way iTunes activiated iPhones with legit SIMs are. One of our readers, Greg, summed it up best in the comments from our last push notification issue post:

<

blockquote>The difference is hacktivation, not jailbreaking. There’s a fair bit of crypto involved in the activation process and the “fixes” so far involve taking certs from other phones. This will only work for so long; eventually people are going to have to be on official carriers and paying official plan rates for Push and YouTube and who knows what they’ll cert off in 3.1 or 4.0?

The Dev Team seem to be working on a fix but it does not appear it will come anytime soon as they've avoided even posting a fix on their blog. Instead, they quietly posted a link on their Twitter page to a very beta fix.

All of this is yet another part of the cat and mouse game, but it's important to try and understand what's going on: normal iPhone users should have nothing to worry about at this time.