https://www.theiphonewiki.com/w/api.php?action=feedcontributions&feedformat=atom&user=AlpineflipThe iPhone Wiki - User contributions [en]2026-04-29T12:49:44ZUser contributionsMediaWiki 1.31.14https://www.theiphonewiki.com/w/index.php?title=Talk:Limera1n&diff=10158Talk:Limera1n2010-10-09T00:29:31Z<p>Alpineflip: /* Who is John Galt? */</p>
<hr />
<div>== Misc. ==<br />
I think some more info may be needed. What is some background on it? I thought Limera1n was a fake from the 3.x days? --[[User:OMEGA RAZER|OMEGA RAZER]] 22:09, 8 October 2010 (UTC)<br />
:It was never fake see [http://theiphonewiki.com/limera1n http://theiphonewiki.com/limera1n] (a cached copy). --[[User:GreySyntax|GreySyntax]] 22:45, 8 October 2010 (UTC)<br />
::Thanks for the clarification. Not sure where I heard that. --[[User:OMEGA RAZER|OMEGA RAZER]] 23:09, 8 October 2010 (UTC)<br />
Geohot made the web page when 3.1.3 come out but he said it used a bootrom exploit for untetherdness that he was saving for the iPhone 4 --[[User:Liamchat|liamchat]] 22:53, 8 October 2010 (UTC)<br />
Anything else we should mention? :P --[[User:Dra1nerdrake|dra1nerdrake]] 23:14, 8 October 2010 (UTC)<br />
:Why the insane secrecy of it? I'm not deep in the scene but this is the first I'm hearing more than the name lol. --[[User:OMEGA RAZER|OMEGA RAZER]] 23:18, 8 October 2010 (UTC)<br />
<br />
== Release ==<br />
<br />
I thought geohot had no plans to release it... [[User:Balloonhead66|Balloonhead66]] 23:22, 8 October 2010 (UTC)<br />
:Correct. Read the controversy section of this page. It should answer as to why the sudden change in heart. ~Drake<br />
<br />
== SIGN YOUR COMMENTS ON THE TALK PAGE ==<br />
Please press the button on top of the exit box or type <nowiki>~~~~</nowiki> manually. This will give you the basic signature. It's also acceptable to just identify yourself. Just make sure we know who you are. ;P ~Drake<br />
<br />
== Latest edit to [[Limera1n]] ==<br />
<br />
How does it look like a tethered? -- Balloonhead66|23:34, October 8, 2010 (UTC)<br />
:They're all plugged in with USB cables. --[[User:OMEGA RAZER|OMEGA RAZER]] 23:35, 8 October 2010 (UTC)<br />
::They could just be charging and he is in the photos app -- Balloonhead66|23:41, October 8, 2010 (UTC)<br />
<br />
== Who is John Galt? ==<br />
<br />
Look at the HTML source of the page. Is this comment new? [[User:Angelo|Angelo]] 23:42, 8 October 2010 (UTC)<br />
:Yep. I've looked at the source of this page before and after this update. The John Galt is probably meant to throw us off. Geohot does that. :P But, yes, it's new. ~Drake<br />
::Where did you see that? [[User:Balloonhead66|Balloonhead66]] 23:50, 8 October 2010 (UTC)<br />
:::Type in Firefox URL bar: view-source:http://limera1n.com/ [[User:Angelo|Angelo]] 23:47, 8 October 2010 (UTC)<br />
::::Or google chrome for that matter :D . Anyway, I thought you meant the source of this page or the [[Limera1n]] page, not the website... *stupid* Thanks for explaining that! [[User:Balloonhead66|Balloonhead66]] 23:50, 8 October 2010 (UTC)<br />
:::::[http://en.wikipedia.org/wiki/John_Galt Who is John Galt] Kind of funny actually when you read it and what's going on right now --[[User:alpineflip|alpineflip]]</div>Alpinefliphttps://www.theiphonewiki.com/w/index.php?title=Talk:Main_Page&diff=9464Talk:Main Page2010-09-24T23:54:09Z<p>Alpineflip: /* Should iH8sn0w be listed as a hacker? */</p>
<hr />
<div>== firmware keys ==<br />
We need a "standard" for firmware key posting so that we can stay organized. Who likes this method?<br />
* [[Kirkwood 7A341 (iPhone 3G)]]<br />
* [[Kirkwood 7A341 (iPod touch 2G)]]<br />
{{unsigned|ChronicDev|02:28, June 18, 2009}}<br />
-----<br />
<br />
Love it. -drg<br />
<br />
anything is better then what we got now --[[User:Posixninja|posixninja]] 05:16, 18 June 2009 (UTC)<br />
<br />
Nice job with the reorganization --[[User:Geohot|geohot]]<br />
<br />
== Should [[User:iH8sn0w|iH8sn0w]] be listed as a hacker? ==<br />
<br />
Stop the edit war, and debate the question here. Otherwise I'll protect the main page. --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 06:05, 23 September 2010 (UTC)<br />
<br />
I think he should because when we are waiting for a jailbreak, he comes out with sn0wbreeze for us to have a jailbreak until there is a full ready to go jailbreak. Just because he creates a GUI for xpwn doesn't mean he shouldn't not be considered a hacker. So stop your whining and you try to make something like that =/. Also by him creating sn0wbreeze, it gives developers time to update their apps for the newest firmware<br />
<br />
I think he should. He uses IDA right? He makes patches? Found the blacksn0w baseband crash - hacker IMHO -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
Disagree. There are lots of other ppl @ the same level as sn0w that aren't listed there. Compared to MN, Geo and planet, he's nowhere near their level. Are we going to list sherif for finding the latest unlock exploit? It's not even up for debate, he doesn't belong there. --[[user:tsuehpsyde|tsuehpsyde]]<br />
<br />
wrong snowbreze is a graphical user interface of xpwn he just got the keys ( another tool that is not his ) and told xpwn to decrypt the .ipsw any one can do that and if ih8sn0w is classed as a hacker then blackthund3r should be as well --[[User:Liamchat|liamchat]] 16:01, 23 September 2010 (UTC)<br />
<br />
I don't think he should be listed, he hasn't contributed anything really except for adding a GUI around xpwn or developing a tool that has already been released by someone else. He doesn't actually create anything on his own and if anyone can remember from before he failed to credit the correct people that created xpwn and claimed that since they weren't around anymore he didn't have too but eventually gave in after Geohot and MuscleNerd plus others got on him saying it wasn't really his work. --[[user:alpineflip|alpineflip]]<br />
<br />
You all made good points and I can't not agree really :D Perhaps we need a developers page then? People like [[User:iH8sn0w|iH8sn0w]] (and possibly myself coming to [[User:liamchat|Liamchat]]'s point) that develop stuff for the iPhone Pwning community but can't be classified as 'hackers' as such but still need recognition. iH8sn0w has worked hard for the community... -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
ok so we need a page to document all app's developed to help those who have just joined iphone community start to learn how jailbreaks actually work and we should have a section documenting all baseband crash developers --[[User:Liamchat|liamchat]] 18:11, 23 September 2010 (UTC)<br />
<br />
Agreed, agreed and agreed... That means that /anyone/ can create something for the [[iPhone]] / [[iPod touch]] and receive credit/attribution and a way of making it available to everyone. It should literally list everyone and what they have contributed - including hackers/real JB devs. Also a page explaining the internals of a jailbreak would be advantageous (and I removed below section as it's being covered here) -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
FWIW, this section was recently added. [http://theiphonewiki.com/wiki/index.php?title=Main_Page&diff=7677&oldid=7661 Here] is where it came into play. I think this is a good section to have on the Main page, but really it should be reserved for notable hackers in the iPhone community. geohot and MuscleNerd both write/work on jailbreaks and unlocks (their own, from scratch), even swapping work on ultrasn0w after geohot opened his source. PlanetBeing has also worked on unlocks (most recently the latest ultrasn0w revision), not to mention his work on Linux for iPhone to get that working. Someone noted earlier in a rev note that geohot isn't on the scene anymore. This is irrelevant, as this is still his Wiki (unless ownership changed?) and he's still hacking on the iPhone. Just because he's not giving you free stuff anymore doesn't mean he isn't involved. He just got tired of people bothering him. Regardless, ih8sn0w is not on the same level as these guys. At all. --[[user:tsuehpsyde|tsuehpsyde]]<br />
<br />
So if the homepage is only for notable hackers where do we put everything / everyone else? We need a categorised page that has sorted developers and what they made. Then anyone can write a program and distribute via the iPhone Wiki. Then everyone gets a mention and anyone can show their tools off without being overshadowed by 'the big boys' -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
a lot of people who make jailbreak's are not mentioned [[User:Zibri]] ( was the first to use the [[AES_Keys]] ) and [[User:ChronicDev]] both made a jailbreak and descoverd an exploit --[[User:Liamchat|liamchat]] 18:48, 23 September 2010 (UTC)<br />
<br />
His tools are mentioned which people can find easily on the main page so they will know who he is but to list him under a category with people like MN, PB, comex, pod2g etc he doesn't even fall close to. Just because you developed an app doesn't mean you are considered a hacker especially if it's not even your work originally! As for the patches in his new version of sn0wbreeze I'm pretty sure msft_guy (not affiliated with any dev teams) released his bundles and by coincidence sn0wbreeze supports the new FW shortly after --[[user:alpineflip|alpineflip]]<br />
<br />
I dont believe iH8sn0w should be considered a hacker. All he does is repackage xpwn into a user-friendly GUI for Windows users and thats it. It's also funny how many naive people see him as being a hacker and they just have complete trust that he'll jailbreak the latest OS. He only recycles current known information. I bet if the dev team found a way to hide their bundles for when the iPhone 4 might be pwnagetool compatible, iH8sn0w will not be able to make sn0wbreeze support it. It's also ridiculous how he just puts up both, donation links and a chipin link for funding for new devices. I believe that that is just being plain abusive. People need to open their eyes and see that iH8sn0w is nothing special. --[[user:gamer765|gamer765]]<br />
<br />
why are we still arguing i and [[User:Windows Helpdesk|blackthund3r]] agreed that [[User:iH8sn0w|iH8sn0w]] is not a hacker ( he may be if he is the first to make the [[Usb_control_msg%280xA1%2C_1%29_Exploit]] work ) but until then i think we need to document the people who are working on tool's to help jailbreak the iphone and ipod's of the world also lot's of jailbreak's where made by random people like the [[LibTiff]] and [[Ramdisk_Hack]] and because they where not made by [[IPhone_Dev_Team]] there where not welcomed like on [[Talk:Ramdisk_Hack]] --[[User:Liamchat|liamchat]] 15:50, 24 September 2010 (UTC)<br />
<br />
the dev team were the first to implement [[Usb_control_msg%280xA1%2C_1%29_Exploit]] discovered by pod2g into redsn0w and released on September 20t; ih8sn0w only mentioned after the fact that he then can include support a day later, and there are plenty of tools out only problem I see is ih8sn0w stuff isn't built very well --[[user:alpineflip|alpineflip]]<br />
<br />
I'm going to go ahead and remove ih8sn0w for now since the general consensus here is that he doesn't belong in that group. Anyone that adds it back in, I will revert their change and point them to the discussion page since most of the people defending his position have not said anything in the discussion. --[[user:tsuehpsyde|tsuehpsyde]]<br />
<br />
So I am not with putting ih8sn0w's name in the hackers list but this guy needs sone appreciations , at least he made something for the jailbreak community that's why I am putting a new "category" called '''iPhone Hacks Developers''' so that ih8sn0w's name will be on this wiki , even if not in the hackers category . I hope this is OK for the most of you , I am gonna wait before posting it so that any one that doesn't like this idea will talk and post in here !! :-)<br />
-ahmadlharb<br />
<br />
Why do we need an 'iPhone Hacks Developers' section on the main page? There's already a section with applications (including sn0wbreeze), which when you click on them, tells you who developed them. Is there some dire need to have ih8sn0w on the main page? If so, I'm not seeing it. --[[user:tsuehpsyde|tsuehpsyde]]<br />
<br />
Honestly, iH8sn0w doesnt even deserve to be in that list either. That list title kinda means that he develops hacks which he does not. A more appropriate title would be "XPwn repackagers" --[[User:gamer765|gamer765]]<br />
<br />
I think he should personally. You have to remember he did more than just repackage xpwn. He created tools for late bootroms that were on 3.1.2 to be jailbroken on new firmwares, though it is tethered. I also think it should go into detail on what each "hacker" does for the community. --[[User:JacobVengeance|JacobVengeance]] 23:41, 24 September 2010 (UTC)<br />
<br />
There is a difference between created and copied, unfortunately none of ih8sn0w's work is original. Like [[User:gamer765|gamer765]] mentioned his applications are listed on the wiki there doesn't need to be a separate category for his stuff or others it's not necessary IMO. --[[user:alpineflip|alpineflip]]</div>Alpinefliphttps://www.theiphonewiki.com/w/index.php?title=Talk:Main_Page&diff=9463Talk:Main Page2010-09-24T23:51:56Z<p>Alpineflip: /* Should iH8sn0w be listed as a hacker? */</p>
<hr />
<div>== firmware keys ==<br />
We need a "standard" for firmware key posting so that we can stay organized. Who likes this method?<br />
* [[Kirkwood 7A341 (iPhone 3G)]]<br />
* [[Kirkwood 7A341 (iPod touch 2G)]]<br />
{{unsigned|ChronicDev|02:28, June 18, 2009}}<br />
-----<br />
<br />
Love it. -drg<br />
<br />
anything is better then what we got now --[[User:Posixninja|posixninja]] 05:16, 18 June 2009 (UTC)<br />
<br />
Nice job with the reorganization --[[User:Geohot|geohot]]<br />
<br />
== Should [[User:iH8sn0w|iH8sn0w]] be listed as a hacker? ==<br />
<br />
Stop the edit war, and debate the question here. Otherwise I'll protect the main page. --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 06:05, 23 September 2010 (UTC)<br />
<br />
I think he should because when we are waiting for a jailbreak, he comes out with sn0wbreeze for us to have a jailbreak until there is a full ready to go jailbreak. Just because he creates a GUI for xpwn doesn't mean he shouldn't not be considered a hacker. So stop your whining and you try to make something like that =/. Also by him creating sn0wbreeze, it gives developers time to update their apps for the newest firmware<br />
<br />
I think he should. He uses IDA right? He makes patches? Found the blacksn0w baseband crash - hacker IMHO -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
Disagree. There are lots of other ppl @ the same level as sn0w that aren't listed there. Compared to MN, Geo and planet, he's nowhere near their level. Are we going to list sherif for finding the latest unlock exploit? It's not even up for debate, he doesn't belong there. --[[user:tsuehpsyde|tsuehpsyde]]<br />
<br />
wrong snowbreze is a graphical user interface of xpwn he just got the keys ( another tool that is not his ) and told xpwn to decrypt the .ipsw any one can do that and if ih8sn0w is classed as a hacker then blackthund3r should be as well --[[User:Liamchat|liamchat]] 16:01, 23 September 2010 (UTC)<br />
<br />
I don't think he should be listed, he hasn't contributed anything really except for adding a GUI around xpwn or developing a tool that has already been released by someone else. He doesn't actually create anything on his own and if anyone can remember from before he failed to credit the correct people that created xpwn and claimed that since they weren't around anymore he didn't have too but eventually gave in after Geohot and MuscleNerd plus others got on him saying it wasn't really his work. --[[user:alpineflip|alpineflip]]<br />
<br />
You all made good points and I can't not agree really :D Perhaps we need a developers page then? People like [[User:iH8sn0w|iH8sn0w]] (and possibly myself coming to [[User:liamchat|Liamchat]]'s point) that develop stuff for the iPhone Pwning community but can't be classified as 'hackers' as such but still need recognition. iH8sn0w has worked hard for the community... -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
ok so we need a page to document all app's developed to help those who have just joined iphone community start to learn how jailbreaks actually work and we should have a section documenting all baseband crash developers --[[User:Liamchat|liamchat]] 18:11, 23 September 2010 (UTC)<br />
<br />
Agreed, agreed and agreed... That means that /anyone/ can create something for the [[iPhone]] / [[iPod touch]] and receive credit/attribution and a way of making it available to everyone. It should literally list everyone and what they have contributed - including hackers/real JB devs. Also a page explaining the internals of a jailbreak would be advantageous (and I removed below section as it's being covered here) -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
FWIW, this section was recently added. [http://theiphonewiki.com/wiki/index.php?title=Main_Page&diff=7677&oldid=7661 Here] is where it came into play. I think this is a good section to have on the Main page, but really it should be reserved for notable hackers in the iPhone community. geohot and MuscleNerd both write/work on jailbreaks and unlocks (their own, from scratch), even swapping work on ultrasn0w after geohot opened his source. PlanetBeing has also worked on unlocks (most recently the latest ultrasn0w revision), not to mention his work on Linux for iPhone to get that working. Someone noted earlier in a rev note that geohot isn't on the scene anymore. This is irrelevant, as this is still his Wiki (unless ownership changed?) and he's still hacking on the iPhone. Just because he's not giving you free stuff anymore doesn't mean he isn't involved. He just got tired of people bothering him. Regardless, ih8sn0w is not on the same level as these guys. At all. --[[user:tsuehpsyde|tsuehpsyde]]<br />
<br />
So if the homepage is only for notable hackers where do we put everything / everyone else? We need a categorised page that has sorted developers and what they made. Then anyone can write a program and distribute via the iPhone Wiki. Then everyone gets a mention and anyone can show their tools off without being overshadowed by 'the big boys' -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
a lot of people who make jailbreak's are not mentioned [[User:Zibri]] ( was the first to use the [[AES_Keys]] ) and [[User:ChronicDev]] both made a jailbreak and descoverd an exploit --[[User:Liamchat|liamchat]] 18:48, 23 September 2010 (UTC)<br />
<br />
His tools are mentioned which people can find easily on the main page so they will know who he is but to list him under a category with people like MN, PB, comex, pod2g etc he doesn't even fall close to. Just because you developed an app doesn't mean you are considered a hacker especially if it's not even your work originally! As for the patches in his new version of sn0wbreeze I'm pretty sure msft_guy (not affiliated with any dev teams) released his bundles and by coincidence sn0wbreeze supports the new FW shortly after --[[user:alpineflip|alpineflip]]<br />
<br />
I dont believe iH8sn0w should be considered a hacker. All he does is repackage xpwn into a user-friendly GUI for Windows users and thats it. It's also funny how many naive people see him as being a hacker and they just have complete trust that he'll jailbreak the latest OS. He only recycles current known information. I bet if the dev team found a way to hide their bundles for when the iPhone 4 might be pwnagetool compatible, iH8sn0w will not be able to make sn0wbreeze support it. It's also ridiculous how he just puts up both, donation links and a chipin link for funding for new devices. I believe that that is just being plain abusive. People need to open their eyes and see that iH8sn0w is nothing special. --[[user:gamer765|gamer765]]<br />
<br />
why are we still arguing i and [[User:Windows Helpdesk|blackthund3r]] agreed that [[User:iH8sn0w|iH8sn0w]] is not a hacker ( he may be if he is the first to make the [[Usb_control_msg%280xA1%2C_1%29_Exploit]] work ) but until then i think we need to document the people who are working on tool's to help jailbreak the iphone and ipod's of the world also lot's of jailbreak's where made by random people like the [[LibTiff]] and [[Ramdisk_Hack]] and because they where not made by [[IPhone_Dev_Team]] there where not welcomed like on [[Talk:Ramdisk_Hack]] --[[User:Liamchat|liamchat]] 15:50, 24 September 2010 (UTC)<br />
<br />
the dev team were the first to implement [[Usb_control_msg%280xA1%2C_1%29_Exploit]] discovered by pod2g into redsn0w and released on September 20t; ih8sn0w only mentioned after the fact that he then can include support a day later, and there are plenty of tools out only problem I see is ih8sn0w stuff isn't built very well --[[user:alpineflip|alpineflip]]<br />
<br />
I'm going to go ahead and remove ih8sn0w for now since the general consensus here is that he doesn't belong in that group. Anyone that adds it back in, I will revert their change and point them to the discussion page since most of the people defending his position have not said anything in the discussion. --[[user:tsuehpsyde|tsuehpsyde]]<br />
<br />
So I am not with putting ih8sn0w's name in the hackers list but this guy needs sone appreciations , at least he made something for the jailbreak community that's why I am putting a new "category" called '''iPhone Hacks Developers''' so that ih8sn0w's name will be on this wiki , even if not in the hackers category . I hope this is OK for the most of you , I am gonna wait before posting it so that any one that doesn't like this idea will talk and post in here !! :-)<br />
-ahmadlharb<br />
<br />
Why do we need an 'iPhone Hacks Developers' section on the main page? There's already a section with applications (including sn0wbreeze), which when you click on them, tells you who developed them. Is there some dire need to have ih8sn0w on the main page? If so, I'm not seeing it. --[[user:tsuehpsyde|tsuehpsyde]]<br />
<br />
Honestly, iH8sn0w doesnt even deserve to be in that list either. That list title kinda means that he develops hacks which he does not. A more appropriate title would be "XPwn repackagers" --[[User:gamer765|gamer765]]<br />
<br />
I think he should personally. You have to remember he did more than just repackage xpwn. He created tools for late bootroms that were on 3.1.2 to be jailbroken on new firmwares, though it is tethered. I also think it should go into detail on what each "hacker" does for the community. --[[User:JacobVengeance|JacobVengeance]] 23:41, 24 September 2010 (UTC)<br />
<br />
There is a difference between created and copied, unfortunately none of ih8sn0w's work is original. Like [[User:gamer765|gamer765]] mentioned his applications are listed on the wiki there doesn't need to be a separate category for his stuff or others it's not necessary IMO.</div>Alpinefliphttps://www.theiphonewiki.com/w/index.php?title=Talk:Main_Page&diff=9450Talk:Main Page2010-09-24T16:08:00Z<p>Alpineflip: /* Should iH8sn0w be listed as a hacker? */</p>
<hr />
<div>== firmware keys ==<br />
We need a "standard" for firmware key posting so that we can stay organized. Who likes this method?<br />
* [[Kirkwood 7A341 (iPhone 3G)]]<br />
* [[Kirkwood 7A341 (iPod touch 2G)]]<br />
{{unsigned|ChronicDev|02:28, June 18, 2009}}<br />
-----<br />
<br />
Love it. -drg<br />
<br />
anything is better then what we got now --[[User:Posixninja|posixninja]] 05:16, 18 June 2009 (UTC)<br />
<br />
Nice job with the reorganization --[[User:Geohot|geohot]]<br />
<br />
== Should [[User:iH8sn0w|iH8sn0w]] be listed as a hacker? ==<br />
<br />
Stop the edit war, and debate the question here. Otherwise I'll protect the main page. --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 06:05, 23 September 2010 (UTC)<br />
<br />
I think he should. He uses IDA right? He makes patches? Found the blacksn0w baseband crash - hacker IMHO -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
Disagree. There are lots of other ppl @ the same level as sn0w that aren't listed there. Compared to MN, Geo and planet, he's nowhere near their level. Are we going to list sherif for finding the latest unlock exploit? It's not even up for debate, he doesn't belong there. --[[user:tsuehpsyde|tsuehpsyde]]<br />
<br />
wrong snowbreze is a graphical user interface of xpwn he just got the keys ( another tool that is not his ) and told xpwn to decrypt the .ipsw any one can do that and if ih8sn0w is classed as a hacker then blackthund3r should be as well --[[User:Liamchat|liamchat]] 16:01, 23 September 2010 (UTC)<br />
<br />
I don't think he should be listed, he hasn't contributed anything really except for adding a GUI around xpwn or developing a tool that has already been released by someone else. He doesn't actually create anything on his own and if anyone can remember from before he failed to credit the correct people that created xpwn and claimed that since they weren't around anymore he didn't have too but eventually gave in after Geohot and MuscleNerd plus others got on him saying it wasn't really his work. --[[user:alpineflip|alpineflip]]<br />
<br />
You all made good points and I can't not agree really :D Perhaps we need a developers page then? People like [[User:iH8sn0w|iH8sn0w]] (and possibly myself coming to [[User:liamchat|Liamchat]]'s point) that develop stuff for the iPhone Pwning community but can't be classified as 'hackers' as such but still need recognition. iH8sn0w has worked hard for the community... -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
ok so we need a page to document all app's developed to help those who have just joined iphone community start to learn how jailbreaks actually work and we should have a section documenting all baseband crash developers --[[User:Liamchat|liamchat]] 18:11, 23 September 2010 (UTC)<br />
<br />
Agreed, agreed and agreed... That means that /anyone/ can create something for the [[iPhone]] / [[iPod touch]] and receive credit/attribution and a way of making it available to everyone. It should literally list everyone and what they have contributed - including hackers/real JB devs. Also a page explaining the internals of a jailbreak would be advantageous (and I removed below section as it's being covered here) -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
FWIW, this section was recently added. [http://theiphonewiki.com/wiki/index.php?title=Main_Page&diff=7677&oldid=7661 Here] is where it came into play. I think this is a good section to have on the Main page, but really it should be reserved for notable hackers in the iPhone community. geohot and MuscleNerd both write/work on jailbreaks and unlocks (their own, from scratch), even swapping work on ultrasn0w after geohot opened his source. PlanetBeing has also worked on unlocks (most recently the latest ultrasn0w revision), not to mention his work on Linux for iPhone to get that working. Someone noted earlier in a rev note that geohot isn't on the scene anymore. This is irrelevant, as this is still his Wiki (unless ownership changed?) and he's still hacking on the iPhone. Just because he's not giving you free stuff anymore doesn't mean he isn't involved. He just got tired of people bothering him. Regardless, ih8sn0w is not on the same level as these guys. At all. --[[user:tsuehpsyde|tsuehpsyde]]<br />
<br />
So if the homepage is only for notable hackers where do we put everything / everyone else? We need a categorised page that has sorted developers and what they made. Then anyone can write a program and distribute via the iPhone Wiki. Then everyone gets a mention and anyone can show their tools off without being overshadowed by 'the big boys' -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
a lot of people who make jailbreak's are not mentioned [[User:Zibri]] ( was the first to use the [[AES_Keys]] ) and [[User:ChronicDev]] both made a jailbreak and descoverd an exploit --[[User:Liamchat|liamchat]] 18:48, 23 September 2010 (UTC)<br />
<br />
His tools are mentioned which people can find easily on the main page so they will know who he is but to list him under a category with people like MN, PB, comex, pod2g etc he doesn't even fall close to. Just because you developed an app doesn't mean you are considered a hacker especially if it's not even your work originally! As for the patches in his new version of sn0wbreeze I'm pretty sure msft_guy (not affiliated with any dev teams) released his bundles and by coincidence sn0wbreeze supports the new FW shortly after --[[user:alpineflip|alpineflip]]<br />
<br />
I dont believe iH8sn0w should be considered a hacker. All he does is repackage xpwn into a user-friendly GUI for Windows users and thats it. It's also funny how many naive people see him as being a hacker and they just have complete trust that he'll jailbreak the latest OS. He only recycles current known information. I bet if the dev team found a way to hide their bundles for when the iPhone 4 might be pwnagetool compatible, iH8sn0w will not be able to make sn0wbreeze support it. It's also ridiculous how he just puts up both, donation links and a chipin link for funding for new devices. I believe that that is just being plain abusive. People need to open their eyes and see that iH8sn0w is nothing special. --[[user:gamer765|gamer765]]<br />
<br />
why are we still arguing i and [[User:Windows Helpdesk|blackthund3r]] agreed that [[User:iH8sn0w|iH8sn0w]] is not a hacker ( he may be if he is the first to make the [[Usb_control_msg%280xA1%2C_1%29_Exploit]] work ) but until then i think we need to document the people who are working on tool's to help jailbreak the iphone and ipod's of the world --[[User:Liamchat|liamchat]] 15:50, 24 September 2010 (UTC)<br />
<br />
the dev team were the first to implement [[Usb_control_msg%280xA1%2C_1%29_Exploit]] discovered by pod2g into redsn0w and released on September 20t; ih8sn0w only mentioned after the fact that he then can include support a day later, and there are plenty of tools out only problem I see is ih8sn0w stuff isn't built very well --[[user:alpineflip|alpineflip]]</div>Alpinefliphttps://www.theiphonewiki.com/w/index.php?title=Talk:Main_Page&diff=9443Talk:Main Page2010-09-23T21:19:19Z<p>Alpineflip: /* Should iH8sn0w be listed as a hacker? */</p>
<hr />
<div>== firmware keys ==<br />
We need a "standard" for firmware key posting so that we can stay organized. Who likes this method?<br />
* [[Kirkwood 7A341 (iPhone 3G)]]<br />
* [[Kirkwood 7A341 (iPod touch 2G)]]<br />
{{unsigned|ChronicDev|02:28, June 18, 2009}}<br />
-----<br />
<br />
Love it. -drg<br />
<br />
anything is better then what we got now --[[User:Posixninja|posixninja]] 05:16, 18 June 2009 (UTC)<br />
<br />
Nice job with the reorganization --[[User:Geohot|geohot]]<br />
<br />
== Should [[User:iH8sn0w|iH8sn0w]] be listed as a hacker? ==<br />
<br />
Stop the edit war, and debate the question here. Otherwise I'll protect the main page. --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 06:05, 23 September 2010 (UTC)<br />
<br />
I think he should. He uses IDA right? He makes patches? Found the blacksn0w baseband crash - hacker IMHO -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
Disagree. There are lots of other ppl @ the same level as sn0w that aren't listed there. Compared to MN, Geo and planet, he's nowhere near their level. Are we going to list sherif for finding the latest unlock exploit? It's not even up for debate, he doesn't belong there. --[[user:tsuehpsyde|tsuehpsyde]]<br />
<br />
wrong snowbreze is a graphical user interface of xpwn he just got the keys ( another tool that is not his ) and told xpwn to decrypt the .ipsw any one can do that and if ih8sn0w is classed as a hacker then blackthund3r should be as well --[[User:Liamchat|liamchat]] 16:01, 23 September 2010 (UTC)<br />
<br />
I don't think he should be listed, he hasn't contributed anything really except for adding a GUI around xpwn or developing a tool that has already been released by someone else. He doesn't actually create anything on his own and if anyone can remember from before he failed to credit the correct people that created xpwn and claimed that since they weren't around anymore he didn't have too but eventually gave in after Geohot and MuscleNerd plus others got on him saying it wasn't really his work. --[[user:alpineflip|alpineflip]]<br />
<br />
You all made good points and I can't not agree really :D Perhaps we need a developers page then? People like [[User:iH8sn0w|iH8sn0w]] (and possibly myself coming to [[User:liamchat|Liamchat]]'s point) that develop stuff for the iPhone Pwning community but can't be classified as 'hackers' as such but still need recognition. iH8sn0w has worked hard for the community... -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
ok so we need a page to document all app's developed to help those who have just joined iphone community start to learn how jailbreaks actually work and we should have a section documenting all baseband crash developers --[[User:Liamchat|liamchat]] 18:11, 23 September 2010 (UTC)<br />
<br />
Agreed, agreed and agreed... That means that /anyone/ can create something for the [[iPhone]] / [[iPod touch]] and receive credit/attribution and a way of making it available to everyone. It should literally list everyone and what they have contributed - including hackers/real JB devs. Also a page explaining the internals of a jailbreak would be advantageous (and I removed below section as it's being covered here) -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
FWIW, this section was recently added. [http://theiphonewiki.com/wiki/index.php?title=Main_Page&diff=7677&oldid=7661 Here] is where it came into play. I think this is a good section to have on the Main page, but really it should be reserved for notable hackers in the iPhone community. geohot and MuscleNerd both write/work on jailbreaks and unlocks (their own, from scratch), even swapping work on ultrasn0w after geohot opened his source. PlanetBeing has also worked on unlocks (most recently the latest ultrasn0w revision), not to mention his work on Linux for iPhone to get that working. Someone noted earlier in a rev note that geohot isn't on the scene anymore. This is irrelevant, as this is still his Wiki (unless ownership changed?) and he's still hacking on the iPhone. Just because he's not giving you free stuff anymore doesn't mean he isn't involved. He just got tired of people bothering him. Regardless, ih8sn0w is not on the same level as these guys. At all. --[[user:tsuehpsyde|tsuehpsyde]]<br />
<br />
So if the homepage is only for notable hackers where do we put everything / everyone else? We need a categorised page that has sorted developers and what they made. Then anyone can write a program and distribute via the iPhone Wiki. Then everyone gets a mention and anyone can show their tools off without being overshadowed by 'the big boys' -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
a lot of people who make jailbreak's are not mentioned [[User:Zibri]] ( was the first to use the [[AES_Keys]] ) and [[User:ChronicDev]] both made a jailbreak and descoverd an exploit --[[User:Liamchat|liamchat]] 18:48, 23 September 2010 (UTC)<br />
<br />
His tools are mentioned which people can find easily on the main page so they will know who he is but to list him under a category with people like MN, PB, comex, pod2g etc he doesn't even fall close to. Just because you developed an app doesn't mean you are considered a hacker especially if it's not even your work originally! As for the patches in his new version of sn0wbreeze I'm pretty sure msft_guy (not affiliated with any dev teams) released his bundles and by coincidence sn0wbreeze supports the new FW shortly after --[[user:alpineflip|alpineflip]]</div>Alpinefliphttps://www.theiphonewiki.com/w/index.php?title=Talk:Main_Page&diff=9442Talk:Main Page2010-09-23T21:17:49Z<p>Alpineflip: /* Should iH8sn0w be listed as a hacker? */</p>
<hr />
<div>== firmware keys ==<br />
We need a "standard" for firmware key posting so that we can stay organized. Who likes this method?<br />
* [[Kirkwood 7A341 (iPhone 3G)]]<br />
* [[Kirkwood 7A341 (iPod touch 2G)]]<br />
{{unsigned|ChronicDev|02:28, June 18, 2009}}<br />
-----<br />
<br />
Love it. -drg<br />
<br />
anything is better then what we got now --[[User:Posixninja|posixninja]] 05:16, 18 June 2009 (UTC)<br />
<br />
Nice job with the reorganization --[[User:Geohot|geohot]]<br />
<br />
== Should [[User:iH8sn0w|iH8sn0w]] be listed as a hacker? ==<br />
<br />
Stop the edit war, and debate the question here. Otherwise I'll protect the main page. --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 06:05, 23 September 2010 (UTC)<br />
<br />
I think he should. He uses IDA right? He makes patches? Found the blacksn0w baseband crash - hacker IMHO -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
Disagree. There are lots of other ppl @ the same level as sn0w that aren't listed there. Compared to MN, Geo and planet, he's nowhere near their level. Are we going to list sherif for finding the latest unlock exploit? It's not even up for debate, he doesn't belong there. --[[user:tsuehpsyde|tsuehpsyde]]<br />
<br />
wrong snowbreze is a graphical user interface of xpwn he just got the keys ( another tool that is not his ) and told xpwn to decrypt the .ipsw any one can do that and if ih8sn0w is classed as a hacker then blackthund3r should be as well --[[User:Liamchat|liamchat]] 16:01, 23 September 2010 (UTC)<br />
<br />
I don't think he should be listed, he hasn't contributed anything really except for adding a GUI around xpwn or developing a tool that has already been released by someone else. He doesn't actually create anything on his own and if anyone can remember from before he failed to credit the correct people that created xpwn and claimed that since they weren't around anymore he didn't have too but eventually gave in after Geohot and MuscleNerd plus others got on him saying it wasn't really his work. --[[user:alpineflip|alpineflip]]<br />
<br />
You all made good points and I can't not agree really :D Perhaps we need a developers page then? People like [[User:iH8sn0w|iH8sn0w]] (and possibly myself coming to [[User:liamchat|Liamchat]]'s point) that develop stuff for the iPhone Pwning community but can't be classified as 'hackers' as such but still need recognition. iH8sn0w has worked hard for the community... -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
ok so we need a page to document all app's developed to help those who have just joined iphone community start to learn how jailbreaks actually work and we should have a section documenting all baseband crash developers --[[User:Liamchat|liamchat]] 18:11, 23 September 2010 (UTC)<br />
<br />
Agreed, agreed and agreed... That means that /anyone/ can create something for the [[iPhone]] / [[iPod touch]] and receive credit/attribution and a way of making it available to everyone. It should literally list everyone and what they have contributed - including hackers/real JB devs. Also a page explaining the internals of a jailbreak would be advantageous (and I removed below section as it's being covered here) -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
FWIW, this section was recently added. [http://theiphonewiki.com/wiki/index.php?title=Main_Page&diff=7677&oldid=7661 Here] is where it came into play. I think this is a good section to have on the Main page, but really it should be reserved for notable hackers in the iPhone community. geohot and MuscleNerd both write/work on jailbreaks and unlocks (their own, from scratch), even swapping work on ultrasn0w after geohot opened his source. PlanetBeing has also worked on unlocks (most recently the latest ultrasn0w revision), not to mention his work on Linux for iPhone to get that working. Someone noted earlier in a rev note that geohot isn't on the scene anymore. This is irrelevant, as this is still his Wiki (unless ownership changed?) and he's still hacking on the iPhone. Just because he's not giving you free stuff anymore doesn't mean he isn't involved. He just got tired of people bothering him. Regardless, ih8sn0w is not on the same level as these guys. At all. --[[user:tsuehpsyde|tsuehpsyde]]<br />
<br />
So if the homepage is only for notable hackers where do we put everything / everyone else? We need a categorised page that has sorted developers and what they made. Then anyone can write a program and distribute via the iPhone Wiki. Then everyone gets a mention and anyone can show their tools off without being overshadowed by 'the big boys' -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
a lot of people who make jailbreak's are not mentioned [[User:Zibri]] ( was the first to use the [[AES_Keys]] ) and [[User:ChronicDev]] both made a jailbreak and descoverd an exploit --[[User:Liamchat|liamchat]] 18:48, 23 September 2010 (UTC)<br />
<br />
His tools are mentioned which people can find easily on the main page so they will know who he is but to list him under a category with people like MN, PB, comex, pod2g etc he doesn't even fall close to. Just because you developed an app doesn't mean you are considered a hacker especially if it's not even your work originally! As for the patches in his new version of sn0wbreez I'm pretty sure msft_guy (not affiliated with any dev teams) released his bundles and by coincidence sn0wbreez supports the new FW shortly after --[[user:alpineflip|alpineflip]]</div>Alpinefliphttps://www.theiphonewiki.com/w/index.php?title=Talk:Main_Page&diff=9441Talk:Main Page2010-09-23T21:02:41Z<p>Alpineflip: /* Should iH8sn0w be listed as a hacker? */</p>
<hr />
<div>== firmware keys ==<br />
We need a "standard" for firmware key posting so that we can stay organized. Who likes this method?<br />
* [[Kirkwood 7A341 (iPhone 3G)]]<br />
* [[Kirkwood 7A341 (iPod touch 2G)]]<br />
{{unsigned|ChronicDev|02:28, June 18, 2009}}<br />
-----<br />
<br />
Love it. -drg<br />
<br />
anything is better then what we got now --[[User:Posixninja|posixninja]] 05:16, 18 June 2009 (UTC)<br />
<br />
Nice job with the reorganization --[[User:Geohot|geohot]]<br />
<br />
== Should [[User:iH8sn0w|iH8sn0w]] be listed as a hacker? ==<br />
<br />
Stop the edit war, and debate the question here. Otherwise I'll protect the main page. --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 06:05, 23 September 2010 (UTC)<br />
<br />
I think he should. He uses IDA right? He makes patches? Found the blacksn0w baseband crash - hacker IMHO -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
Disagree. There are lots of other ppl @ the same level as sn0w that aren't listed there. Compared to MN, Geo and planet, he's nowhere near their level. Are we going to list sherif for finding the latest unlock exploit? It's not even up for debate, he doesn't belong there. --[[user:tsuehpsyde|tsuehpsyde]]<br />
<br />
wrong snowbreze is a graphical user interface of xpwn he just got the keys ( another tool that is not his ) and told xpwn to decrypt the .ipsw any one can do that and if ih8sn0w is classed as a hacker then blackthund3r should be as well --[[User:Liamchat|liamchat]] 16:01, 23 September 2010 (UTC)<br />
<br />
I don't think he should be listed, he hasn't contributed anything really except for adding a GUI around xpwn or developing a tool that has already been released by someone else. He doesn't actually create anything on his own and if anyone can remember from before he failed to credit the correct people that created xpwn and claimed that since they weren't around anymore he didn't have too but eventually gave in after Geohot and MuscleNerd plus others got on him saying it wasn't really his work. --[[user:alpineflip|alpineflip]]<br />
<br />
You all made good points and I can't not agree really :D Perhaps we need a developers page then? People like [[User:iH8sn0w|iH8sn0w]] (and possibly myself coming to [[User:liamchat|Liamchat]]'s point) that develop stuff for the iPhone Pwning community but can't be classified as 'hackers' as such but still need recognition. iH8sn0w has worked hard for the community... -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
ok so we need a page to document all app's developed to help those who have just joined iphone community start to learn how jailbreaks actually work and we should have a section documenting all baseband crash developers --[[User:Liamchat|liamchat]] 18:11, 23 September 2010 (UTC)<br />
<br />
Agreed, agreed and agreed... That means that /anyone/ can create something for the [[iPhone]] / [[iPod touch]] and receive credit/attribution and a way of making it available to everyone. It should literally list everyone and what they have contributed - including hackers/real JB devs. Also a page explaining the internals of a jailbreak would be advantageous (and I removed below section as it's being covered here) -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
FWIW, this section was recently added. [http://theiphonewiki.com/wiki/index.php?title=Main_Page&diff=7677&oldid=7661 Here] is where it came into play. I think this is a good section to have on the Main page, but really it should be reserved for notable hackers in the iPhone community. geohot and MuscleNerd both write/work on jailbreaks and unlocks (their own, from scratch), even swapping work on ultrasn0w after geohot opened his source. PlanetBeing has also worked on unlocks (most recently the latest ultrasn0w revision), not to mention his work on Linux for iPhone to get that working. Someone noted earlier in a rev note that geohot isn't on the scene anymore. This is irrelevant, as this is still his Wiki (unless ownership changed?) and he's still hacking on the iPhone. Just because he's not giving you free stuff anymore doesn't mean he isn't involved. He just got tired of people bothering him. Regardless, ih8sn0w is not on the same level as these guys. At all. --[[user:tsuehpsyde|tsuehpsyde]]<br />
<br />
So if the homepage is only for notable hackers where do we put everything / everyone else? We need a categorised page that has sorted developers and what they made. Then anyone can write a program and distribute via the iPhone Wiki. Then everyone gets a mention and anyone can show their tools off without being overshadowed by 'the big boys' -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
a lot of people who make jailbreak's are not mentioned [[User:Zibri]] ( was the first to use the [[AES_Keys]] ) and [[User:ChronicDev]] both made a jailbreak and descoverd an exploit --[[User:Liamchat|liamchat]] 18:48, 23 September 2010 (UTC)<br />
<br />
His tools are mentioned which people can find easily on the main page so they will know who he is but to list him under a category with people like MN, PB, comex, pod2g etc he doesn't even fall close to. Just because you developed an app doesn't mean you are considered a hacker especially if it's not even your work originally! --[[user:alpineflip|alpineflip]]</div>Alpinefliphttps://www.theiphonewiki.com/w/index.php?title=Talk:Main_Page&diff=9426Talk:Main Page2010-09-23T17:47:01Z<p>Alpineflip: /* Should iH8sn0w be listed as a hacker? */</p>
<hr />
<div>== firmware keys ==<br />
We need a "standard" for firmware key posting so that we can stay organized. Who likes this method?<br />
* [[Kirkwood 7A341 (iPhone 3G)]]<br />
* [[Kirkwood 7A341 (iPod touch 2G)]]<br />
{{unsigned|ChronicDev|02:28, June 18, 2009}}<br />
-----<br />
<br />
Love it. -drg<br />
<br />
anything is better then what we got now --[[User:Posixninja|posixninja]] 05:16, 18 June 2009 (UTC)<br />
<br />
Nice job with the reorganization --[[User:Geohot|geohot]]<br />
<br />
== Should [[User:iH8sn0w|iH8sn0w]] be listed as a hacker? ==<br />
<br />
Stop the edit war, and debate the question here. Otherwise I'll protect the main page. --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 06:05, 23 September 2010 (UTC)<br />
<br />
I think he should. He uses IDA right? He makes patches? Found the blacksn0w baseband crash - hacker IMHO -- [[User:Windows Helpdesk|blackthund3r]]<br />
<br />
Disagree. There are lots of other ppl @ the same level as sn0w that aren't listed there. Compared to MN, Geo and planet, he's nowhere near their level. Are we going to list sherif for finding the latest unlock exploit? It's not even up for debate, he doesn't belong there. --[[user:tsuehpsyde|tsuehpsyde]]<br />
<br />
wrong snowbreze is a graphical user interface of xpwn he just got the keys ( another tool that is not his ) and told xpwn to decrypt the .ipsw any one can do that and if ih8sn0w is classed as a hacker then blackthund3r should be as well --[[User:Liamchat|liamchat]] 16:01, 23 September 2010 (UTC)<br />
<br />
I don't think he should be listed, he hasn't contributed anything really except for adding a GUI around xpwn or developing a tool that has already been released by someone else. He doesn't actually create anything on his own and if anyone can remember from before he failed to credit the correct people that created xpwn and claimed that since they weren't around anymore he didn't have too but eventually gave in after Geohot and MuscleNerd plus others got on him saying it wasn't really his work. --[[user:alpineflip|alpineflip]]<br />
<br />
== Dev Teams ==<br />
What constitutes a hacker and what constitutes a Dev Team?? iH8sn0w, for instance, hasn't made any exploits/found vulnerabilities but still makes JB tools. Then you get all sorts of dev teams that would add themselves for publicity for a program that is basically a substandard version of recovery mode controller -- [[User:Windows Helpdesk|blackthund3r]]</div>Alpinefliphttps://www.theiphonewiki.com/w/index.php?title=FaceTime&diff=9055FaceTime2010-09-08T00:28:25Z<p>Alpineflip: /* FaceTime Registration Request */</p>
<hr />
<div>== General ==<br />
<br />
FaceTime is iChat AV for iPhone and iPod touch (latest generation only). Jobs presented an "alphabet soup" of technologies that were involved in making FaceTime work, many of which are shared with iChat AV, including:<br />
<br />
* H.264 and AAC, its ISO/MPEG video and audio codecs (just like iChat).<br />
* [https://wiki.tools.ietf.org/html/rfc3261 SIP (Session Initiation Protocol)], the open IETF signaling protocol for VoIP used by iChat AV.<br />
* STUN (Session Traversal Utilities for NAT), an IETF standard for dealing with lots of different kinds of NAT.<br />
* TURN (Traversal Using Relay NAT), an IETF standard for allowing a client behind NAT to receive incoming requests like a server.<br />
* ICE (Interactive Connectivity Establishment) an IETF standard which helps set up connections through NAT firewalls.<br />
* RTP (Real-time Transport Protocol), an iETF standard for delivering media streams in VoIP.<br />
* SRTP (Secure RTP) an IETF standard designed to provide encryption, message authentication and integrity for the data streams.<br />
<br />
FaceTime uses ports 53, 80, 443, 4080, 5223, and 16393-16472 (UDP).<br />
<br />
== FaceTime Activation / Registration ==<br />
<br />
FaceTime is activated by sending a couple of SMS text messages in the background between the iPhone and an Apple server. If your carrier does not officially support the iPhone 4, you may be charged for sending the activation SMS to an international (UK) number. Your carrier might also have issues delivering the SMS correctly which will prevent FaceTime from activating.<br />
<br />
After enabling FaceTime in iPhone settings, your iPhone will attempt to send a "silent text message" (i. e. a text you don't know about) to Apple, that registers your telephone number on Apple's servers used for FaceTime. Apple then returns a "silent coded text message" to your iPhone, that activates the FaceTime within iOS4.<br />
<br />
After being activated, FaceTime will happily operate solely over WiFi. However, FaceTime activation currently requires the iPhone to be activated, have an active SIM card with the ability to send and receive SMSes. If there's an issue sending or receiving SMS messages, FaceTime can't be enabled or activated.<br />
<br />
FaceTime will work successfully in Airplane Mode over WiFi, however it requires FaceTime to be activated, and a SIM card inserted in your device.<br />
<br />
=== FaceTime Registration Request ===<br />
<br />
The iPhone sends a Registration Request SMS silently to this UK number (as identified by the [http://en.wikipedia.org/wiki/%2B44_%28country_code%29 +44 country code]): +44 7786 205094. AT&T customers have their own local number for FaceTime activations: 28818773. In Bell and Telus carrier bundles, version 7.2 the number is: 49988.<br />
<br />
The Activation Servers number (PhoneNumberRegistrationGatewayAddress) is set in carrier.plist in System/Library/Carrier Bundles/<Your carrier>.bundle (or Unknown.bundle):<br />
<br />
<pre><br />
<key>PhoneNumberRegistrationGatewayAddress</key><br />
<string>+447786205094</string><br />
</pre><br />
<br />
You can change this to i. e. your own number and FaceTime will send the FaceTime Registration Request SMS to your own number.<br />
<br />
Some carrier bundles (i.e. T-Mobile Germany Carrier Update 7.1) also contain the following key. It sets the notification to display a message about SMS chargers might be applied when trying to activate FaceTime.<br />
<pre><br />
<key>RegistrationOptInRequired</key><br />
<true/><br />
</pre><br />
<br />
Registration Request:<br />
<pre><br />
REG-REQ?v=2;t=char[64];i=char[40];r=char[8]<br />
</pre><br />
<br />
Registration Request Example:<br />
<pre><br />
REG-REQ?v=2;t=0C11F1ACF776391387797F5EEC1B87E9FC33DAD9 B86583270B8E8DDE78A7A23C;i=2CFA805D9A0D1D43CE57429 B4DA8E454B9AADB5D;r=5917c44d<br />
</pre><br />
It was noticed the last portion i= has different character for every FaceTime request.<br />
<br />
The Request is saved on:<br />
<br />
* /var/wireless/spool/MobileOriginated/s.sms.1073741825 (or another identifier) <br />
<br />
FaceTime will continue to retry sending the activation SMS multiple times before failing. [http://discussions.apple.com/thread.jspa?threadID=2483442&start=15&tstart=150][http://modmyi.com/forums/t-mobile/722445-iphone-4-t-mobile-users-beware-international-text-charges-facetime.html#post5380385]<br />
<br />
=== FaceTime Registration Response ===<br />
<br />
If your carrier doesn't officially support silent SMS messages, you may see the FaceTime Registration Response messages displayed.<br />
<br />
Registration Response:<br />
<pre><br />
¿¿¿¿y¿¿REG-RESP?v=2;r=XXXXXXX;n=+XXXXXXXXX;s=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br />
</pre><br />
<br />
(X are numbers and codes received, it looks like a password and a hash code).<br />
<br />
== Packet Capture - original from [http://fryguypa.wordpress.com/2010/06/25/iphone-4-and-facetime/ FryGuy's Blog] ==<br />
<br />
* 1st iPhone IP Private – 192.168.0.128<br />
* 1st iPhone IP NAT – 216.164.100.100<br />
* 2nd iPhone IP Private 192.168.2.106<br />
* 2nd iPhone IP NAT – 72.81.200.200<br />
<br />
Note: NATs changed to protect the guilty<br />
<br />
=== Packets ===<br />
<pre><br />
No. Time Source Destination Protocol Info<br />
1 0.000000 192.168.0.128 17.155.5.251 UDP Source port: 16402 Destination port: connected<br />
2 0.431054 17.155.5.251 192.168.0.128 UDP Source port: connected Destination port: 16402<br />
3 0.715713 192.168.0.128 17.155.5.251 UDP Source port: 51136 Destination port: connected<br />
4 0.716064 192.168.0.128 17.155.5.251 UDP Source port: 51136 Destination port: 16385<br />
5 0.717147 192.168.0.128 17.155.5.252 UDP Source port: 51136 Destination port: 16386<br />
6 0.958285 17.155.5.252 192.168.0.128 UDP Source port: 16386 Destination port: 51136<br />
7 0.960329 17.155.5.251 192.168.0.128 UDP Source port: 16385 Destination port: 51136<br />
8 0.960588 17.155.5.251 192.168.0.128 UDP Source port: connected Destination port: 51136<br />
9 1.016402 192.168.0.128 216.164.100.100 UDP Source port: 51136 Destination port: 52585<br />
10 1.018172 192.168.0.128 216.164.100.100 UDP Source port: 51136 Destination port: 52585<br />
11 1.019912 192.168.0.128 17.155.4.14 TCP 50697 > https [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=2 TSV=469580285 TSER=0<br />
12 1.020140 192.168.0.128 216.164.100.100 UDP Source port: 51136 Destination port: 52585<br />
13 1.298294 17.155.4.14 192.168.0.128 TCP https > 50697 [SYN, ACK] Seq=0 Ack=1 Win=8190 Len=0 MSS=1360 WS=4<br />
14 1.318312 192.168.0.128 17.155.4.14 TCP 50697 > https [ACK] Seq=1 Ack=1 Win=131920 Len=0<br />
15 1.321211 192.168.0.128 17.155.4.14 TLSv1 Client Hello<br />
16 1.645657 192.168.0.128 17.155.5.251 UDP Source port: 51136 Destination port: connected<br />
17 1.645978 192.168.0.128 17.155.5.251 UDP Source port: 51136 Destination port: 16385<br />
18 1.646130 192.168.0.128 17.155.5.252 UDP Source port: 51136 Destination port: 16386<br />
19 1.662234 192.168.0.128 208.59.216.10 TCP 50698 > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=2 TSV=469580291 TSER=0<br />
20 1.730834 17.155.4.14 192.168.0.128 TCP [TCP segment of a reassembled PDU]<br />
21 1.731963 17.155.4.14 192.168.0.128 TLSv1 Server Hello, Certificate, Server Hello Done<br />
22 1.808298 208.59.216.10 192.168.0.128 TCP http > 50698 [SYN, ACK] Seq=0 Ack=1 Win=5792 Len=0 MSS=1380 TSV=941715237 TSER=469580291 WS=1<br />
23 1.832208 192.168.0.128 17.155.4.14 TCP 50697 > https [ACK] Seq=160 Ack=1361 Win=130560 Len=0<br />
24 1.834588 192.168.0.128 17.155.4.14 TCP 50697 > https [ACK] Seq=160 Ack=2490 Win=130788 Len=0<br />
25 1.834954 192.168.0.128 208.59.216.10 TCP 50698 > http [ACK] Seq=1 Ack=1 Win=131328 Len=0 TSV=469580293 TSER=941715237<br />
26 1.836526 192.168.0.128 208.59.216.10 HTTP GET /WebObjects/VCInit.woa/wa/getBag?ix=1 HTTP/1.1 <br />
27 1.881018 17.155.5.252 192.168.0.128 UDP Source port: 16386 Destination port: 51136<br />
28 1.882147 17.155.5.251 192.168.0.128 UDP Source port: connected Destination port: 51136<br />
29 1.883124 17.155.5.251 192.168.0.128 UDP Source port: 16385 Destination port: 51136<br />
30 1.884207 192.168.0.128 216.164.100.100 UDP Source port: 51136 Destination port: 52585<br />
31 1.886053 192.168.0.128 216.164.100.100 UDP Source port: 51136 Destination port: 52585<br />
32 1.886343 192.168.0.128 216.164.100.100 UDP Source port: 51136 Destination port: 52585<br />
33 1.930729 192.168.0.128 17.155.4.14 TLSv1 Client Key Exchange<br />
34 1.930835 192.168.0.128 17.155.4.14 TLSv1 Change Cipher Spec<br />
35 1.931583 192.168.0.128 17.155.4.14 TLSv1 Encrypted Handshake Message<br />
36 2.190008 208.59.216.10 192.168.0.128 TCP http > 50698 [ACK] Seq=1 Ack=229 Win=6432 Len=0 TSV=941715619 TSER=469580293<br />
37 2.190313 208.59.216.10 192.168.0.128 TCP [TCP segment of a reassembled PDU]<br />
38 2.191366 208.59.216.10 192.168.0.128 TCP [TCP segment of a reassembled PDU]<br />
39 2.192312 208.59.216.10 192.168.0.128 HTTP/XML HTTP/1.1 200 OK <br />
40 2.242678 192.168.0.128 208.59.216.10 TCP 50698 > http [ACK] Seq=229 Ack=2737 Win=128592 Len=0 TSV=469580297 TSER=941715619<br />
41 2.243014 192.168.0.128 208.59.216.10 TCP 50698 > http [ACK] Seq=229 Ack=3506 Win=127820 Len=0 TSV=469580297 TSER=941715619<br />
42 2.393275 17.155.4.14 192.168.0.128 TCP https > 50697 [ACK] Seq=2490 Ack=299 Win=35216 Len=0<br />
43 2.393305 17.155.4.14 192.168.0.128 TCP https > 50697 [ACK] Seq=2490 Ack=305 Win=35216 Len=0<br />
44 2.393351 17.155.4.14 192.168.0.128 TCP https > 50697 [ACK] Seq=2490 Ack=342 Win=35184 Len=0<br />
45 2.394633 17.155.4.14 192.168.0.128 TLSv1 Change Cipher Spec, Encrypted Handshake Message<br />
46 2.448112 192.168.0.128 17.155.4.14 TCP 50697 > https [ACK] Seq=342 Ack=2533 Win=131876 Len=0<br />
47 2.449760 192.168.0.128 17.155.4.14 TLSv1 Application Data<br />
48 2.450325 192.168.0.128 17.155.4.14 TLSv1 Application Data<br />
49 2.511448 192.168.0.128 17.155.5.251 UDP Source port: 51136 Destination port: connected<br />
50 2.512608 192.168.0.128 17.155.5.251 UDP Source port: 51136 Destination port: 16385<br />
51 2.512776 192.168.0.128 17.155.5.252 UDP Source port: 51136 Destination port: 16386<br />
52 2.905644 17.155.5.252 192.168.0.128 UDP Source port: 16386 Destination port: 51136<br />
53 2.905690 17.155.4.14 192.168.0.128 TCP https > 50697 [ACK] Seq=2533 Ack=966 Win=34560 Len=0<br />
54 2.905782 17.155.4.14 192.168.0.128 TCP https > 50697 [ACK] Seq=2533 Ack=1453 Win=34064 Len=0<br />
55 2.906896 17.155.5.251 192.168.0.128 UDP Source port: 16385 Destination port: 51136<br />
56 2.907536 17.155.5.251 192.168.0.128 UDP Source port: connected Destination port: 51136<br />
57 2.923466 17.155.4.14 192.168.0.128 TLSv1 Application Data<br />
58 2.923924 17.155.4.14 192.168.0.128 TLSv1 Application Data<br />
59 3.060254 192.168.0.128 216.164.100.100 UDP Source port: 51136 Destination port: 52585<br />
60 3.060422 192.168.0.128 216.164.100.100 UDP Source port: 51136 Destination port: 52585<br />
61 3.062146 192.168.0.128 17.155.4.14 TCP 50697 > https [ACK] Seq=1453 Ack=2894 Win=131556 Len=0<br />
62 3.062451 192.168.0.128 17.155.4.14 TCP 50697 > https [ACK] Seq=1453 Ack=3240 Win=131212 Len=0<br />
63 3.062741 192.168.0.128 199.7.52.190 TCP 50699 > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=2 TSV=469580305 TSER=0<br />
64 3.063122 192.168.0.128 216.164.100.100 UDP Source port: 51136 Destination port: 52585<br />
65 3.532458 199.7.52.190 192.168.0.128 TCP http > 50699 [SYN, ACK] Seq=0 Ack=1 Win=8190 Len=0 MSS=1380<br />
66 3.571122 192.168.0.128 199.7.52.190 TCP 50699 > http [ACK] Seq=1 Ack=1 Win=65535 Len=0<br />
67 3.579117 192.168.0.128 199.7.52.190 HTTP GET /EVIntl2006.cer HTTP/1.1 <br />
68 3.690690 192.168.0.128 17.155.4.14 TLSv1 Encrypted Alert<br />
69 3.692505 192.168.0.128 17.155.5.251 UDP Source port: 51136 Destination port: connected<br />
70 3.696701 192.168.0.128 17.155.4.14 TCP 50697 > https [FIN, ACK] Seq=1476 Ack=3240 Win=131920 Len=0<br />
71 3.697007 192.168.0.128 208.59.216.10 TCP 50698 > http [FIN, ACK] Seq=229 Ack=3506 Win=131328 Len=0 TSV=469580312 TSER=941715619<br />
72 3.697388 192.168.0.128 17.155.5.251 UDP Source port: 51136 Destination port: 16385<br />
73 3.697617 192.168.0.128 17.155.5.252 UDP Source port: 51136 Destination port: 16386<br />
74 3.809626 199.7.52.190 192.168.0.128 TCP [TCP segment of a reassembled PDU]<br />
75 3.810572 199.7.52.190 192.168.0.128 HTTP HTTP/1.0 200 OK (text/plain)<br />
76 3.881720 192.168.0.128 199.7.52.190 TCP 50699 > http [ACK] Seq=154 Ack=1865 Win=65535 Len=0<br />
77 3.890585 192.168.0.128 199.7.52.190 TCP 50699 > http [FIN, ACK] Seq=154 Ack=1865 Win=65535 Len=0<br />
78 3.952258 208.59.216.10 192.168.0.128 TCP http > 50698 [FIN, ACK] Seq=3506 Ack=230 Win=6432 Len=0 TSV=941717381 TSER=469580312<br />
79 3.954256 192.168.0.128 208.59.216.10 TCP 50698 > http [ACK] Seq=230 Ack=3507 Win=131328 Len=0 TSV=469580314 TSER=941717381<br />
80 4.007781 17.155.4.14 192.168.0.128 TCP https > 50697 [ACK] Seq=3240 Ack=1476 Win=40928 Len=0<br />
81 4.007965 17.155.4.14 192.168.0.128 TCP https > 50697 [FIN, ACK] Seq=3240 Ack=1477 Win=40928 Len=0<br />
82 4.009155 17.155.5.251 192.168.0.128 UDP Source port: 16385 Destination port: 51136<br />
83 4.009170 17.155.5.251 192.168.0.128 UDP Source port: connected Destination port: 51136<br />
84 4.009948 192.168.0.128 17.155.4.14 TCP 50697 > https [FIN, ACK] Seq=1476 Ack=3240 Win=131920 Len=0<br />
85 4.014495 192.168.0.128 17.155.4.14 TCP 50697 > https [ACK] Seq=1477 Ack=3241 Win=131920 Len=0<br />
86 4.019866 192.168.0.128 216.164.100.100 UDP Source port: 51136 Destination port: 52585<br />
87 4.023955 17.155.5.252 192.168.0.128 UDP Source port: 16386 Destination port: 51136<br />
88 4.025984 192.168.0.128 216.164.100.100 UDP Source port: 51136 Destination port: 52585<br />
89 4.034971 192.168.0.128 216.164.100.100 UDP Source port: 51136 Destination port: 52585<br />
90 4.504292 199.7.52.190 192.168.0.128 TCP http > 50699 [ACK] Seq=1865 Ack=155 Win=8190 Len=0<br />
91 4.671800 192.168.0.128 17.155.5.251 UDP Source port: 51136 Destination port: connected<br />
92 4.672167 192.168.0.128 17.155.5.251 UDP Source port: 51136 Destination port: 16385<br />
93 4.672411 192.168.0.128 17.155.5.252 UDP Source port: 51136 Destination port: 16386<br />
94 5.139092 17.155.5.252 192.168.0.128 UDP Source port: 16386 Destination port: 51136<br />
95 5.140068 17.155.5.251 192.168.0.128 UDP Source port: 16385 Destination port: 51136<br />
96 5.140129 17.155.5.251 192.168.0.128 UDP Source port: connected Destination port: 51136<br />
97 5.210011 192.168.0.128 216.164.100.100 UDP Source port: 51136 Destination port: 52585<br />
98 5.215809 192.168.0.128 216.164.100.100 UDP Source port: 51136 Destination port: 52585<br />
99 5.216068 192.168.0.128 216.164.100.100 UDP Source port: 51136 Destination port: 52585<br />
100 5.715774 192.168.0.128 17.155.5.251 UDP Source port: 51136 Destination port: 16385<br />
101 6.054578 17.155.5.251 192.168.0.128 UDP Source port: 16385 Destination port: 51136<br />
102 8.258196 192.168.0.128 192.168.2.106 STUN2 Binding Request<br />
103 8.286606 192.168.0.128 192.168.2.106 STUN2 Binding Request<br />
104 8.303893 192.168.0.128 72.81.200.200 STUN2 Binding Request<br />
105 8.313353 192.168.0.128 192.168.2.106 STUN2 Binding Request<br />
106 8.313582 72.81.200.200 192.168.0.128 STUN2 Binding Request<br />
107 8.316909 192.168.0.128 72.81.200.200 STUN2 Binding Success Response<br />
108 8.333677 192.168.0.128 72.81.200.200 STUN2 Binding Request<br />
109 8.344419 72.81.200.200 192.168.0.128 STUN2 Binding Request<br />
110 8.350980 192.168.0.128 72.81.200.200 STUN2 Binding Success Response<br />
111 8.360852 192.168.0.128 72.81.200.200 STUN2 Binding Request<br />
112 8.374294 72.81.200.200 192.168.0.128 STUN2 Binding Request<br />
113 8.376750 192.168.0.128 72.81.200.200 STUN2 Binding Success Response<br />
114 8.467002 192.168.0.128 192.168.2.106 STUN2 Binding Request<br />
115 8.496083 192.168.0.128 192.168.2.106 STUN2 Binding Request<br />
116 8.528156 72.81.200.200 192.168.0.128 STUN2 Binding Request<br />
117 8.530139 192.168.0.128 72.81.200.200 STUN2 Binding Request<br />
118 8.530765 192.168.0.128 72.81.200.200 STUN2 Binding Success Response<br />
119 8.553316 72.81.200.200 192.168.0.128 STUN2 Binding Request<br />
120 8.555467 192.168.0.128 72.81.200.200 STUN2 Binding Request<br />
121 8.556032 192.168.0.128 72.81.200.200 STUN2 Binding Success Response<br />
122 8.626234 72.81.200.200 192.168.0.128 STUN2 Binding Success Response<br />
123 8.629896 72.81.200.200 192.168.0.128 STUN2 Binding Success Response123<br />
124 8.730361 192.168.0.128 72.81.200.200 SIP/SDP Request: INVITE sip:user@72.81.200.200:50925, with session description<br />
125 8.748746 72.81.200.200 192.168.0.128 STUN2 Binding Success Response<br />
126 8.771618 192.168.0.128 192.168.2.106 STUN2 Binding Request<br />
127 8.797557 192.168.0.128 192.168.2.106 STUN2 Binding Request<br />
128 8.925571 72.81.200.200 192.168.0.128 STUN2 Binding Success Response<br />
129 8.927723 72.81.200.200 192.168.0.128 STUN2 Binding Success Response<br />
130 9.232700 192.168.0.128 72.81.200.200 SIP/SDP Request: INVITE sip:user@72.81.200.200:50925, with session description<br />
131 9.258562 192.168.0.128 192.168.2.106 STUN2 Binding Request<br />
132 9.262926 72.81.200.200 192.168.0.128 SIP Status: 100 Trying<br />
133 9.268831 72.81.200.200 192.168.0.128 SIP Status: 180 Ringing<br />
134 9.296692 192.168.0.128 192.168.2.106 STUN2 Binding Request<br />
135 9.320586 72.81.200.200 192.168.0.128 SIP/SDP Status: 200 OK, with session description<br />
136 9.326857 192.168.0.128 72.81.200.200 SIP Request: ACK sip:user@72.81.200.200:50925<br />
137 9.334699 192.168.0.128 72.81.200.200 SIP Request: MESSAGE sip:user@72.81.200.200:50925<br />
138 9.688477 72.81.200.200 192.168.0.128 SIP/SDP Status: 200 OK, with session description<br />
139 9.716567 192.168.0.128 72.81.200.200 SIP Request: ACK sip:user@72.81.200.200:50925<br />
140 9.834542 192.168.0.128 72.81.200.200 SIP Request: MESSAGE sip:user@72.81.200.200:50925<br />
141 10.216053 72.81.200.200 192.168.0.128 SIP Status: 200 OK<br />
142 10.230152 192.168.0.128 72.81.200.200 SIP Request: MESSAGE sip:user@72.81.200.200:50925<br />
143 10.442848 72.81.200.200 192.168.0.128 SIP Status: 200 OK<br />
144 10.491689 72.81.200.200 192.168.0.128 SIP Status: 200 OK<br />
145 10.727812 192.168.0.128 72.81.200.200 SIP Request: MESSAGE sip:user@72.81.200.200:50925<br />
146 11.229984 192.168.0.128 72.81.200.200 SIP Request: MESSAGE sip:user@72.81.200.200:50925<br />
147 11.318007 72.81.200.200 192.168.0.128 SIP Status: 200 OK<br />
148 11.367565 192.168.0.128 72.81.200.200 SIP Request: MESSAGE sip:user@72.81.200.200:50925<br />
149 11.618986 72.81.200.200 192.168.0.128 SIP Status: 200 OK<br />
150 11.866691 192.168.0.128 72.81.200.200 SIP Request: MESSAGE sip:user@72.81.200.200:50925<br />
151 11.998932 192.168.0.128 72.81.200.200 UDP Source port: 16402 Destination port: 50925<br />
152 12.035444 72.81.200.200 192.168.0.128 SIP Status: 200 OK<br />
153 12.063916 192.168.0.128 72.81.200.200 UDP Source port: 16402 Destination port: 50925<br />
154 12.129174 192.168.0.128 72.81.200.200 UDP Source port: 16402 Destination port: 50925<br />
155 12.180258 192.168.0.128 72.81.200.200 UDP Source port: 16402 Destination port: 50925<br />
156 12.183416 192.168.0.128 72.81.200.200 UDP Source port: 16402 Destination port: 50925<br />
157 12.187093 72.81.200.200 192.168.0.128 SIP Status: 200 OK<br />
158 12.195043 192.168.0.128 72.81.200.200 UDP Source port: 16402 Destination port: 50925<br />
159 12.200932 72.81.200.200 192.168.0.128 SIP Request: BYE sip:user@192.168.0.128:16402<br />
160 12.206181 192.168.0.128 72.81.200.200 SIP Status: 200 OK<br />
</pre><br />
<br />
=== Comments (by FryGuy) ===<br />
<br />
==== Packets 1 – 10 ====<br />
* The phones communicates to a server at Apple (17.155.5.251 is what I saw). Communication is sourced from port 16402 via UDP initially and then looks to dynamically allocate ports for communication (16385 and 16386 are what appeared on my end).<br />
<br />
==== Packets 11 – 101 ====<br />
<br />
* The phone then negotiates an HTTPS connection to the servers at Apple for the setup and communication. There also seems to be some communication to other servers (in this case i see RCN 208.59.216.10) – and they are my cable provider.<br />
<br />
==== Packets 102 – 123 ====<br />
<br />
* After Client (iPhone) and server negotiation you start to see Stun requests via the private IPs, after they fail you see them from the Public IP NAT ranges. They success via the Public peering at that point.<br />
<br />
==== Packets 124 – 160 ====<br />
<br />
* A SIP call is then initiated between the phones for the video portion of the call<br />
<br />
== How does Apples (FaceTime) Server know the IP Address of the 2nd (to be called) iPhone ? ==<br />
<br />
Easy, every iPhone registers itself at Apple whenever Wifi is available ("calls" Home).<br />
<br />
Basic Process:<br />
<br />
* iPhone senses Wifi Connection<br />
* iPhone gets IP Adress i.e. via DHCP<br />
* iPhone sends HTTP Request to www.apple.com/library/test/success.html<br />
* iPhone receives HTTP Response (HTML Page containing "Success" in the Body part - without hyphens)<br />
* iPhone knows it is connected to the Internet<br />
* (iPhone gets iphone-wu.apple.com/7day/v2/latest/lto2.dat)<br />
* iPhone contacts init.ess.apple.com<br />
* iPhone contacts EVIntl-aia.verisign.com/EVIntl2006.cer<br />
* iPhone joins Apples "Jabber" Server 17.149.36.99<br />
* Apple knows iPhones IP - this is used for FaceTime (and Push Notifications I would think)<br />
<br />
== Additional Information ==<br />
<br />
* Interesting Packet Trace & Discussion: http://blog.roychowdhury.org/2010/06/25/facetime-on-iphone-4-vanilla-unencrypted-stun-and-sip/<br />
* Excellent Analysis: http://www.packetstan.com/<br />
* Highly Rumorous: http://www.addictivetips.com/mobile/apple-gathering-facetime-information-ability-to-see-video-calls/</div>Alpineflip