Siri port GUI On i4,3G,iPod Touch 4

to port the Siri GUI to the iPhone, iPod Touch and iPad. These files contained everything necessary to get Siri’s GUI functioning on unsupported iDevices. The only aspect of this port that does not work is actually the ability talk to Siri; this is because Siri can not yet contact Apple’s servers. As Siri cannot currently contact Apple’s servers why would one go to the trouble of installing it?

Well the developer who released these files claimed that there were some files included he would not show us how to get functioning at this time. It is in my opinion that these files may contain the key to getting Siri to contact Apple’s servers. Even if I am not right about these files, once you install the GUI to your iPhone, iPod Touch or iPad, all it takes is another developer to release the activation files and you will have already done a brunt of the work to get Siri fully functioning on your iDevice.

If you are ever going to be interested in porting Siri to your:

• iPhone 4
• iPhone 3GS
• iPod Touch 4G
• iPad 1G

We suggest following this how to guide on installing the Siri GUI files to your unsupported Apple iDevices. That way you will be prepared for when an activation method has been found, and it will be an easy task to get Siri fully functioning.

How To Install Siri On iPhone, iPod Touch & iPad

Before you start this how to guide you will need to download the following:

• Siri GUI files
• AssistantServices.framework file (Try this if the one downloaded with the Siri GUI files did not work)
• iExplorer (Apple iOS File Manager For Mac OS X and Windows)

Step 1) - The first thing you will need to do is update to the iOS 5 firmware and then Jailbreak your iPhone, iPod Touch and iPad running the iOS 5 firmware.

Step 2) - The next thing you will need to do is open iExplorer and navigate to the followingdirectory:

/Root Directory/System/Library/PrivateFrameworks/

Once in the directory you will need to transfer the AssistantServices.framework folder into thedirectory specified above.

Step 3) – You will now need to navigate to the following directory:

/Root Directory/System/Library/CoreServices/SpringBoard.app/

Once inside the directory you will need to transfer the contents of the SpringBoard_Assistant_picsfolders into the above directory.

Step 4) – The next thing you will need to do is edit the SpringBoard .plist file. It will be namedN81AP for the fourth generation iPod touch and N9x for iPhone 4 (x may be 0, 1, 2 depending on whether you are installing Siri on an iPhone 3GS or iPhone 4).

To edit this file you will need to drag it to your desktop and open the file in a text editor program. Once the file is open look for the following line:

<key>720p</key>
<true/>

Underneath that line you will need to add the following line:

<key>assistant</key>
<true/>

Once the line has been added you will need to save the file and then transfer it back to your iPhone, iPod Touch or iPad.

Note: An alternative method to manually editing the file on your computer would be to use an application like iFile.

Step 5) - Now you must simply restart your iPhone, iPod Touch or iPad.

Note: As you have a tethered Jailbreak you will need to boot your iDevice using RedSn0w(Mac/Windows).

Upon restarting your iDevice you can hold down the home button and you should notice Siri appears. Congratulations! You have just installed the Siri GUI on your iPhone, iPod Touch or iPad. We will keep you updated when more information is discovered on how to enable Siri to contact Apple’s servers. Until that time enjoy showing off to your friends that you have Siri your iDevice.

Let us know if you have any questions in the comments section below…

UPDATE #1: Try this AssistantServices.framework file if the one downloaded with the Siri GUI files did not work.

Siri

Just a few days ago mobile app development firm applidium managed to crack the Siri protocol. While this does not mean anything for Siri on older iOS devices, it’s still quite interesting. What they’ve done allows virtually any device to interact with Siri’s servers. Unfortunately, to accomplish this you’ll need some data from a real iPhone 4S. Applidium’s tutorial for doing this is not very in-depth, so I thought I’d post a slightly more in-depth guide to getting the necessary data from an iPhone 4S. This guide assumes that you’ll be running Mac OS X 10.7.2, but in theory any UNIX operating system should work with a few simple tweaks.

1. EDIT: Also forgot to mention that you’ll need to install a few ruby gems for the ruby scripts to work. Run the following commands in Terminal to get those:

   sudo gem install eventmachine
   sudo gem install CFPropertyList

2. EDIT 2: You’ll also need libxml2, openssl, and zlib installed. I used MacPorts for this, but you can install however you’d like.
3. First you should download the tools that applidium so graciously posted on github.
4. Put those downloaded tools aside for now, and open up Terminal (If you don’t know what that is you should probably give up right now) and change the current directory to your desktop (or whatever directory you’d like to work in).
5. We’re going to need to create fake SSL certificates to spoof your iPhone 4S into thinking that your computer is actually Siri’s servers. You’ll need openssl installed (I believe it’s installed by default on Mac OS X).
6. Generate your certificate authority by entering the following into Terminal:

   openssl genrsa -des3 -out ca.key 4096
   openssl req -new -x509 -days 365 -key ca.key -out ca.crt

7. Next you’ll need to generate your server key and request for signing. Make sure to enter guzzoni.apple.com as the Common Name.

   openssl genrsa -des3 -out server.key 4096 openssl req -new -key server.key -out server.csr
   

8. Now we can sign our certificate request using our certificate authority

   openssl x509 -req -days 365 -in server.csr -CA ca.crt -CAkey ca.key -set_serial 01 -out server.passless.crt

9. Now we need to create a version of the server key that doesn’t cause a prompt for a password

   openssl rsa -in server.key -out server.key.insecure
   mv server.key server.key.secure
   mv server.key.insecure server.passless.key

10. OK, now that we have our certificate’s we can transfer the certificate authority to your iPhone 4S so that it will accept our custom server as Siri’s server. To do this you’ll need the iPhone Configuration Utility which can be found here (Mac only).
11. Once that's downloaded open it up and connect your iPhone 4S to your computer, select File, then New Configuration Profile.
12. In the General section enter guzzoni.apple.com as the name, and anything you want in the identifier field (i.e. com.company.profile).
13. Select the Credentials section and click Configure.
14. Then navigate to the ca.crt file we created earlier and select that.
15. Now select your iPhone 4S in the source list on the right side of the window and select the Configuration Profiles tab.
16. Next to the profile we just created, select Install.
17. You should now be prompted on your iPhone 4S to install then approve the certificate. Do that.
18. Now we'll need to setup a fake DNS server on your computer to fool your iPhone into thinking that your computer is the Siri server. To do this download the python script found here and save it as dns.py.
19. Open that file up in your text editor of choice and go to line 29 and change the IP to the local IP address of your computer.
20. Now in Terminal go to the directory where that python script is and enter the following:

    sudo python dns.py

21. Now back on your iPhone 4S, go to Settings > WiFi and connect to the same network as your computer.
22. Now tap the blue arrow next to the WiFi signal to configure options.
23. In the DNS Server field enter the IP address of your computer.
24. Now back on your computer open a new Terminal window (leave dns.py running!) and go to the directory with the files we downloaded in the first step. Also make sure that server.passless.key and server.passless.crt are in this directory as well.
25. Enter the following into the new Terminal window:

    sudo ruby siriServer.rb

26. Now back on your iPhone 4S make a dictation request with Siri. For example, go to the Notes app and tap the microphone next to the space bar and say something.
27. If everything worked you should see a bunch of text in the Terminal window. This will give you everything you need to get Siri to authenticate using the other various tools downloaded in step 1. You'll want to replace all the instances of COMMENTED_OUT in the ruby scripts with the data that was dumped into Terminal.

Please note that this tutorial does not illustrate how to get Siri working on older iOS devices, it simply tells you how to get the necessary authentication information from a live iPhone 4S. You can use what you've learned here to communicate with Siri from your Mac, and essentially any other device using the tools provided in step 1.

4sGamers in the app store

4sGamers
Forum is based off the website of www.4ugamers.com
its the newest gamers forum out right now get in and start playing showing off your game play ,computer skills , post your cheat codes
and many more !

on the Register if you don't see the verification code 
please visit www.4ugamers.com to sign up 4sGamers

Weapons of Mass Exploitation

Greetings, friends & jailbreakers!
It has now been several months since OPK and I (posixninja) took the stage at JailbreakCon (fka MyGreatFest) in London. Since then, I & other members of the Chronic Dev team have been keeping quietly busy on many fronts, so I thought it was about time to give you all a brief update.

Update on iOS5 Jailbreak

First & foremost: during my JailbreakCon talk in September, I was excited to announce that the Chronic Dev team had already discovered 5 different exploits for use in our upcoming jailbreak. Unfortunately, that announcement was a bit premature, because in the subsequent weeks, Apple found & patched a (critical) few of those exploits, between the beta versions we used for testing and the final release of iOS5 on October 12.

Sadly (and trust us, we are much more sad about this than any of you could possibly be), this has prevented us from being able to release a new jailbreak as quickly as we wanted to. As I hinted at earlier this week on Twitter, I was initially disheartened to think that so many of the countless hours we’ve worked on this jailbreak seemingly went right down the drain.

Not to mention, these are by no means the first exploits that have been “lost” by Chronic Dev (or any other iOS hacking teams) in this manner. In fact, these are just a few in a long-running series of exploits that were patched by Apple before we hackers could make use of them in a free jailbreak for you, our loyal fans.

Well, to be frank… this is bullshit!!! And now, Chronic Dev is ready to turn this little information battle into an all-out, no-holds-barred information WAR. So we want to use this experience as an opportunity to explain the method Apple uses to find potential vulnerabilities, as well as to unveil our new master plan, which should not only prevent this from happening to us again in the future, but also allow us to use all of you to find more exploits, so we can ultimately get an untethered jailbreak into your hands as quickly as possible.

How Apple Finds Exploits

One of the primary challenges in working with userland exploits is that, every time any program crashes on your iPhone, a “crash report” is generated and instantly sent back to Apple. As you can imagine, while we’re working out all the kinks in the exploitation of a vulnerability, we may need to crash any particular program thousands & thousands of times.

It’s possible to change your iTunes settings to stop sending this diagnostic information back to Apple, and of course everyone in Chronic Dev has made this change on all our development machines. However, even this is not always 100% effective at preventing Apple from obtaining our data. For instance, if one of us is at a friend’s house and plugs our iPhone up to his or her computer (even just to charge it), it’s very likely that computer is set up to send all our valuable data & crash reports right back to Apple.

As a side note, this is also the primary reason we’re unable to perform or allow any public beta testing of our software before it’s released. Any potential beta tester could be unknowingly sending crash reports back to Apple, which would prematurely alert the company to our exploits & the discovery of their vulnerabilities before we even have the chance to release.

Help Us Help You: Send Us Your Crash Reports

Instead of allowing this vicious cycle to continue, we decided to write a new program to turn Apple’s own beast against its master, per se. All this program requires from you is to attach your iOS device to your computer and click a single button!

At this point, the program copies all the crash reports off your device (which, under normal circumstances, would be sent right back to Apple), and instead sends this data to a secure, private server hosted by your friendly Chronic Dev team. Next, our program proceeds to neuter your copy of iTunes, simply by changing your settings to prevent your computer from sending any further diagnostic information from your device to Apple.

Using this agglomeration of your crash reports and our ninja skills, Chronic Dev will be able to quickly pinpoint vulnerabilities in various programs by using the same techniques Apple currently employs. At the very least, your data will help point us in the direction of which applications are the most vulnerable, so we can focus our time & energy on these with laser-like intensity. And, of course, this will also prevent Apple from accessing all your valuable data, just so they can then turn around and use it against you.

Thank You!

Many thanks in advance for your prompt response & help in this effort, your continued support of GreenPois0n & the Chronic Dev team, and your patience while we continue our never-ending, diligent work on your (free!! coming soon!) untethered jailbreak for iOS5 and/or iPhone 4S.

One final THANKS! While I have spent many of my own hours on the development, design & programming of this tool, especially the back-end, I also owe a great debt of gratitude to:

• C-Dev hacker Nikias & his lovely wife Hanene – for the many tedious hours they spent programming the front-end & user-friendly interface;
• C-Dev member OPK – for his graphic design work & the brilliant logo for this app; and
• Chronic-Dev, LLC – for graciously hosting the servers where we will store the (fingers crossed) millions of crash reports and other data that you all are going to send us momentarily, via this link…

[cdev_reporter-mac-1.0_beta.zip]

[PLEASE NOTE: This link is to the Mac beta version of our software. An updated/final Mac version as well as a Windows version will be available in the next 24 hours.]

Finally, we will be making a more concerted effort to keep you updated on our progress in the days & weeks to come, so keep checking back here on our blog! And don’t forget to follow the official Twitter feeds of both theChronic Dev team as well as my personal (p0sixninja) account.

[cdev_reporter-mac-1.0_beta.zep