Showing posts with label IOS. Show all posts
Showing posts with label IOS. Show all posts
[How To] - Untethered JailBreak iOS 5.0.1 For A4 Devices Only
Finally, the day has arrived. The much awaited exploit from @Pod2G which was in development from few days is now released from DevTeam. You can apply the untethered from the tweak which has instantaneously come up in Cydia from @P0sixninja. If you are currently using a tethered JailBreak on iOS 5.0/iOS 5.0.1, open Cydia, search for ‘Corona’ and install it. After the reboot, you would be on an untethered JailBreak.
iPhone3GS
iPhone4
iPhone4-CDMA
iPad1
iPod touch 3G
iPod touch 4G
However, you always have the other alternative. You can download the recently updated Redsn0w from the DevTeam, run it over the tethered JailBroken iDevice , follow the instructions and you are done. Only the following A4 based devices are supported :
iPhone3GS
iPhone4
iPhone4-CDMA
iPad1
iPod touch 3G
iPod touch 4G
Google Launches Google Currents For Android Phones & and iOS To Compete Flipboard
Today, Google announced its latest app, a content news reader for Android phones and tablets (and iOS) called Google Currents. Google Currents lets you explore online magazines and other content from your device in a whole new way. You can think of Google Currents as a direct competitor Flipboard, the popular RSS reader for iOS.
iOS 5.1 Failed To Resolve Battery Problems
Apple has not experienced everything going their way despite seeing iPhone 4S topping the sales chart. The iCloud and iOS has still undergone a variety of issues. With the release of iOS 5 , many users where able to fix long-standing issues but one thing that it failed to do is to solve the battery life problem.
Apple has participated in the discussion by confirming that iOS 5 still possess problems but also informed that they are trying to fix the problem. And we thought the battery drain issue would now be over when iOS 5.0.1 was seeded to testers. But that did not happen and the issue even spread to those who were not previous sufferers before.
Apple has participated in the discussion by confirming that iOS 5 still possess problems but also informed that they are trying to fix the problem. And we thought the battery drain issue would now be over when iOS 5.0.1 was seeded to testers. But that did not happen and the issue even spread to those who were not previous sufferers before.
What Exactly IS Carrier IQ ?
Ever since a researcher named Trevor Eckhart posted evidence that a program known as Carrier IQ is tracking mobile users’ keystrokes and activities, the Web has been abuzz trying to find out how much the program actually collects and how widespread it is.
Carrier IQ is an analytics program for mobile devices that advertises to carriers that it can “measure performance and user experience with no visible impact to your customers.” Eckhart, using his own HTC device, found that the program not only records information about app activity and battery life but also notes when users press any key on the phone and records text messages. He said the data is transmitted back to Carrier IQ’s servers.That seems to contradict a statement from Carrier IQ, which clearly said that it doesn’t record keystrokes. The company also said it does not provide tracking tools, inspect or report the content of communications or provide real-time data reporting to its customers.
Carrier IQ On Your iOS 5 Device
Carrier IQ, the now infamous “rootkit” or “keylogger”, is not just for Android, Symbian, BlackBerry, and even webOS. In fact, up through and including iOS 5, Apple has included a copy of Carrier IQ on the iPhone. However, it does appears to be disabled along with diagnostics enabled on iOS 5; older versions may send back information in more cases. Because of that, if you want to disable Carrier IQ on your iOS 5 device, turning off “Diagnostics and Usage” in Settings appears to be enough.
I do realize the info below is a bit technical, but that’s the best way for me to share what I’ve figured out so far at this point. Please feel free to let me know if you discover something else here.Carrier IQ is run from a number of different daemons, depending on the firmware version of the device: (You can view this on a jailbroken iPhone with iFile or extract it from a software update bundle if you want to check the files out yourself.)
- iOS 3: /usr/bin/IQAgent
- iOS 4 and 5: /usr/bin/awd_ice2 or /usr/bin/awd_ice3
The startup routine verifies that it is running on either a compatible device and exits if it is not. In addition, and most importantly: it appears it will only run if:
- iOS 3: The DiagnosticsAllowed key is set to true in the com.apple.iqagent preferences — which it does not appear to be enabled on any of my devices. (If anyone knows what would cause this key to be set to true, please let me know.)
- iOS 4: Unknown, probably like iOS 3.
- iOS 5: Copies the ShouldSubmit value from lockdownd, under the domain com.apple.MobileDeviceCrashCopy. I believe this value is set by the “Submit Logs to Apple” option during the iOS 5 setup sequence, and so Carrier IQ logging is toggled with that setting.
Hidden Secrets Revealed in Apple's iOS 5
iOS 5 introduces a wealth of new features that can be used to aid people with visual, aural, and mobility impairments. You’ll find these options on the Accessibility setting screen under Settings -> General -> Accessibility. But Apple’s iOS 5 mobile operating system still having few secrets which are not told to consumers which we are revealing inthis article. Developers and sleuthing hackers have been hard at work since Apple released the OS in October unearthing a number of hidden features and tweaking the OS to do things it was never intended to do.Here are 5 Hidden Apple’s iOS 5 secrets revealed that may surprise you.
How To: Emulate Cisco ASA in GNS3
In this article, I will show you how to emulate Cisco ASA using Qemu. Once again, please note that ASA is not provided and will not be. So please don’t ask. Also be aware that ASA does not 100% work in Qemu but that’s enough to play with it.
Installation
First compile and patch Qemu as you would do for running JunOS. This will give us pcap, lcap and UDP tunnels (i.e. GNS3/Dynamips connections) capabilities.
Then obtain ASA itself. If you are smart and patient you will find it. I used asa802-k8.bin for my installations. As far as I know, nobody has been able to run ASA > version 8.2 (ASA keeps rebooting).
The next step is to get an initrd and a Linux kernel (inside the initrd) from your ASA image to use them with Qemu and also fix the initrd for our needs. The initrd is zipped and archived in the ASA image, we have to extract it.
There are 2 ways, manually or using a tool I created.
First compile and patch Qemu as you would do for running JunOS. This will give us pcap, lcap and UDP tunnels (i.e. GNS3/Dynamips connections) capabilities.
Then obtain ASA itself. If you are smart and patient you will find it. I used asa802-k8.bin for my installations. As far as I know, nobody has been able to run ASA > version 8.2 (ASA keeps rebooting).
The next step is to get an initrd and a Linux kernel (inside the initrd) from your ASA image to use them with Qemu and also fix the initrd for our needs. The initrd is zipped and archived in the ASA image, we have to extract it.
There are 2 ways, manually or using a tool I created.
How To - Step By Step Installation of JunOS on GNS3 [Part 4]
Testing
To check if everything work, let’s configure 2 Olives:
root@%cli
root>edit
[edit]
root#
[edit]
root#set system root-authentication plain-text-password
New password:
Retype new password:
[edit]
root#set interfaces em0 unit 0 family inet address 10.0.0.1/8
[edit]
root#commit
commit completeConfigure the other device using the same commands but with another IP address (e.g. 10.0.0.2/8) and ping.
How To - Step By Step Installation of JunOS on GNS3 [Part 3]
Updating JunOS
You can update your version of JunOS from the CLI with the following command:
request system software add [jinstall_package]
Running your router(s)
Now you have a base olive image. Qemu allows you to use this as a base for other images and only writing the changes to your “slave” images saving on disk space! You can also use less memory for each Qemu instance.
Create a new image off of your base image. Repeat for all your routers you want to emulate:
qemu-img create -b olive-base.img -f qcow2 R1.img
Start your router and then telnet to it:
Now you have a base olive image. Qemu allows you to use this as a base for other images and only writing the changes to your “slave” images saving on disk space! You can also use less memory for each Qemu instance.
Create a new image off of your base image. Repeat for all your routers you want to emulate:
qemu-img create -b olive-base.img -f qcow2 R1.img
Start your router and then telnet to it:
2001 Once logged in, you can type “cli” to launch the JunOS command line interpreter, exit to … exit and halt to shutdown FreeBSD. Remember to kill your qemu instance(s).
qemu R1.img -m 96 -nographic -daemonize -serial telnet::2001,server,nowait \
-localtime -net nic,macaddr=00:aa:00:60:01:01,model=e1000 -net user telnet localhost
How To - Step By Step Installation of JunOS on GNS3 [Part 1]
This article explain you how to emulate Juniper JunOS on a PC using Qemu. This is an updated and enhanced version of excellent howtos from Juniper Clue and Internetwork Pro as well asHimawan Nugroho’s blog. I mainly focused on Qemu, so if you wish to install JunOS on a real PC or using VMware, please have a look at the Juniper Clue article for more information (and of course Google).
So what’s new you would say? First, I chose to use the latest version of Qemu: the 0.11.0 which supports the Intel e1000 network card emulation since version 0.10.0. and includes several fixes for it. I have modified and adapted the old patch for Qemu 0.11.0, it includes the UDP tunnel (connection to Dynamips/GNS3), PCAP and LCAP support. Also, the patch allows multicast traffic with the e1000, i82557b and i82559er Qemu emulated network cards. Moreover, this article show how to emulate JunOS on multiple operating systems: Mac OS X, Windows XP and Linux Ubuntu 9.04 without using an untrustworthy obscure binary downloaded from a forum you can’t even read the language
So what’s new you would say? First, I chose to use the latest version of Qemu: the 0.11.0 which supports the Intel e1000 network card emulation since version 0.10.0. and includes several fixes for it. I have modified and adapted the old patch for Qemu 0.11.0, it includes the UDP tunnel (connection to Dynamips/GNS3), PCAP and LCAP support. Also, the patch allows multicast traffic with the e1000, i82557b and i82559er Qemu emulated network cards. Moreover, this article show how to emulate JunOS on multiple operating systems: Mac OS X, Windows XP and Linux Ubuntu 9.04 without using an untrustworthy obscure binary downloaded from a forum you can’t even read the language
GNS3 Installation Hypervisor Load Balancing - 2
GNS3 Installation Hypervisor Load Balancing - 1
THIS PROCEDURE MADE UP WITHIN MULTIPLE PARTS:
1. Directory structure 2. GNS3 configurations
3. Configure Hypervisor
4. Edit Dynamips on the client
5. Edit Dynamips on the Server
6. Start Dynamips on SVR and Client
7. Start GNS3 and create simple topology
3. Configure Hypervisor
4. Edit Dynamips on the client
5. Edit Dynamips on the Server
6. Start Dynamips on SVR and Client
7. Start GNS3 and create simple topology
Subscribe to:
Posts (Atom)
