Nice attack on an bad implementation of using the Atmel SAM7XC Crypto Co-Processor

http://oamajormal.blogspot.co.uk/2013/02/atmel-sam7xc-crypto-co-processor-key.html

This is why hardware key management is so important. In this case the processor contains hardware cryptographic engines yet no dedicated key storage or tamper protection. This means that keys have to be stored in internal Flash or RAM which opens up vulnerabilities allowing keys to be extracted.

A proper secure processor implements dedicated key storage memory combined with active tamper detection. If a tamper event is detected by the processors security sub-system; then the key storage area will be actively cleared preventing key extraction. Examples of these processors include the Maxim USIP, Freescale i.MX258 or the Broadcom BCM5982.

The analysis performed here validates how much implementation matters when designing a secure system.

iOS 6.x Untethered Jailbreak out

Available at: http://evasi0n.com/

I recommend checking the SHA-1 hash of the release you downloaded against the provided list (a habit I should get into as well). This can be performed by using OpenSSL:
openssl sha1 <filename>

Interesting that the jailbreak steps are different from the "redsn0w" utility, not having to get the device into DFU mode is great as I muck it up every time and have to reboot.
The installer places a "Jailbreak" icon onto the SpringBoard as part of the process which has to be clicked, i'm interested to know what role this performs in the jailbreak process.

Make sure if you've jailbroken your device to change the your default root password to something you've chosen! we don't want this happening again.

ssh root@<ip of your device>
iPhone:~ root# passwd

Changing password for root.
New password:

and heres a great writeup of what the jailbreak does:
http://blog.accuvantlabs.com/blog/bthomas/evasi0n-jailbreaks-userland-component

Hooking objective-c internals using the Captain Hook framework.

One of the fun things to do with a Jailbroken iPhone is to install custom themes using the "WinterBoard" application.
This allows you to install themes such as: Auxo which customises the application switcher bar or Boss.ios which alters the whole look of the interface.

How does "Winterboard" work?

The "WinterBoard" application works by "hooking" the existing internal classes using the Objective-C Runtime Library. This library is loaded by all Objective-C applications to support the dynamic features of the language which means that we can utlilise is to perform our own alterations to the OS and applications.

This allows for the alteration of icons, sounds and textures without having to touch the originals supplied with the device. This means that you can alter the device without the risk of breaking the device.

The CaptainHook framework

This is a header file created by Ryan Petrich(http://rpetri.ch/) to assist with the creation of hooking libraries using the Objective-C runtime. This provides a functions to assist in the setting up of custom hooking code. Documentation is a little scant so hopefully this blog can help you begin to create your own hooks.

Getting started

I've altered the sample code provided at the Github as the function used has been depreciated by Apple
hook source code and a makefile

#import <CaptainHook/CaptainHook.h>

CHDeclareClass(NSString); //set up the Captain Hook Library

//function called when hook is encountered

CHMethod(4, void, NSString, writeToFile, NSString *, path,  

         atomically, BOOL, useAuxiliaryFile, encoding,  

         NSStringEncoding, end, error, NSError **, error) 

{

  NSLog(@"Writing string to %@: %@", path, self);

  //send received arguments to the original class

  CHSuper(4, NSString, writeToFile, path, atomically,

  useAuxiliaryFile, encoding, end, error, error);

}

//create the hook

CHConstructor

{

  CHLoadClass(NSString); //setup the class

  //hook the chosen method

  CHHook(4, NSString, writeToFile, atomically, encoding, 

  error);

}

Heres a sample program you can test it with:
link to test program and makefile

#import <Foundation/Foundation.h>

#import <Foundation/NSString.h>

int main(void) {

  NSAutoreleasePool *pool = \

    [[NSAutoreleasePool alloc] init];

  NSString *testString = @"Hello, I am the test string";

  [testString 

    writeToFile:@"test.txt" 

    atomically:YES 

    encoding:NSASCIIStringEncoding 

    error:NULL];

  [pool release];

  return 0;

}

Compiling

Compiling works on OS X with xCode 4.x and iOS SDK version 6.0 in the default library locations.
Copy the compiled "testhook" and "stringHook.dylib" to your device. SSH in, export DYLD_INSERT_LIBRARIES and then execute "testhook" e.g:

  desktop$ scp ./hooktest ./stringHook.dylib \

root@<device ip>:/var/root/

  desktop$ ssh root@<device ip>

  device # export \

DYLD_INSERT_LIBRARIES="/var/root/stringHook.dylib"

  device # /var/root/hooktest

And you should see:

  2013-02-01 21:40:58.710 hooktest[562:707] Writing string to   

  test.txt: Hello, I am the test string

Which only works for command line apps as export DYLD... does not get performed by SpringBoard

A bit of explanation

The CHMethod function declaration is:

  CHMethod(number of inputs, return type, class name, name1, type1, 

  arg1, name2, type2, arg2 ...(number of inputs));

An easy way to fill this method is to take the method definition, and fill it in left to right e.g.

  [NSString writeToFile: atomically: encoding: error:]

  -(BOOL)writeToFile:(NSString *)path atomically:   

  (BOOL)useAuxiliaryFile encoding:(NSStringEncoding)enc error   

  (NSError **)error

translates to:

  CHMethod(4, void, NSString, writeToFile, NSString *, path,    

  atomically, BOOL, useAuxiliaryFile, encoding, NSStringEncoding, 

end, error, NSError **, error)

We set the return type to void as for the example we don't return anything

The function declaration of CHSuper and CHHook are:

CHSuper(number of inputs, class name, name1, arg1, name2,
arg2 ...(number of inputs)

CHHook(number of inputs, class name,name1,name2,
...(num of inputs)

Other ways of inserting the injection library

Using launchctl seems to be a great way.
launchctl setenv DYLD_INSERT_LIBRARIES "/path/to/dylib"
which can be used for individual SpringBoard apps
or you can insert this plist key into one of the plists in "/System/Library/LaunchDaemons/"
although be careful! i screwed up my SpringBoard.plist editing it which caused the SpringBoard to stop loading(i.e no icons), so make a backup of the file just to be sure.
<key>EnvironmentVariables</key>
<dict>
<key>DYLD_FORCE_FLAT_NAMESPACE</key>
<string>1</string>
<key>DYLD_INSERT_LIBRARIES</key>
<string>/path/to/dylib</string>
</dict>
reload the plist using
launchctl unload <chosen plist>
then reload
launchctl load <chosen plist>

Another easy method is to install MobileSubstrate and copy the dylib to "/Library/MobileSubstrate/DynamicLibraries" and reload the SpringBoard. MobileSubstrate loads all the dylibs in this folder automatically.

Heres another piece of sample hooking code i created playing this stuff: https://github.com/peterfillmore/touchHook
This changes the status bar each time a touch is detected.

A great use of this hooking in security testing has been recently released by Jeremy Allen which uses it to disable certificate verification. http://intrepidusgroup.com/insight/2013/01/scorched-earth-how-to-really-disable-certificate-verification-on-ios/
So play around with it and see what fun you can have.