AIM Push Problems - Hacktivated iPhones to Blame?

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.

Jeremy

Community editor. Tech enthusiast. All-around geek.

More Posts

 

0
loading...
0
loading...
0
loading...
0
loading...

← Previously

Microsoft Store to Compete With Apple Store -- By Not Selling Anything

Next up →

Quick App: Spash ID for iPhone - Save that Important Data Securely

Reader comments

AIM Push Problems - Hacktivated iPhones to Blame?

11 Comments
Sort by Rating

@Mark - Have you had any issues with a normal iPhone? There is no mention to whether or not Schadde has an altered iPhone. My guess is he does since he communicates with Dev Team members on Twitter. Personally I have not heard of a untouched iPhone having push issues.

I used Redsn0w to jailbreak and then Ultrasn0w to unlock, and all of my Push apps (Beejive, IM+, Yahoo and MobileMe) with the 3.0 update all work great - I don't understand what some are doing wrong for their PNS not to work.

My iPhone is non-hacktivated and I get random push notifications from beejive all the time and most of the time I'm not even getting a message to look at.

@Dmys - the reason your phone would be hacktivated is if it were unlocked to be used on another carrier.

Push Notifications have worked swimmingly for me. I'm very happy with the service but I also restored and unjailbroke my phone the day before 3.0 came out. So, I have a relatively clean install and I'm unjailbroken. I currently have no plans to go back but with all of this news I can guarantee that I will stick with the Apple approved software. The JB apps caused some major stability issues for my iPhone anyway.