Lion, Time Machine and AFP feature bits.

Update2: SMB should be supported in _r2 version. Probably not a very good idea unless your network connection is solid. Also remember that you can't restore the whole system from a TM image on an SMB share.. at least not from OS X boot disk.
Update1: Please try updating your NAS firmware first; most manufacturers will be releasing updates that make their devices Lion-compatible in the near future.
These new flags made mandatory in Lion help with AFP session recovery after network connection loss, so you will be at a higher risk of data corruption when using this workaround over spotty WiFi.

'The network backup disk does not support the required AFP features' message means that
Lion's backupd now requires 'TM Lock Stealing' and 'Server Reply Cache' AFP features on all TM destinations.

TMShowUnsupportedNetworkVolumes workaround affects the UI but has no effect on actual daemon behaviour.
So, seeing as how I'm not going to buy a Time Capsule any time soon, an idea was born:
What if we could make backupd work with those unsupported volumes and unleash any potentially data-munching-monster-ish bugs this unsupportedness shall surely entail? Sounds like a plan!

tldr: Download, unzip and run the script.

^^ A dylib that fakes those new shiny AFP feature bits for your old musty half-dead early 20th century NAS-o-saurus.

Disclaimer: Use at your own risk; data-corru¾*{5Ë# may occur!

Boring tech details: just read the source.

Ultrasn0w (with preserved baseband) on 4.3..

NO NEW UNLOCKS HERE! FOR USERS WITH BB VERSIONS CURRENTLY SUPPORTED BY ultrasn0w ONLY! PLEASE RTFM!

4.3 seems to have enabled slidable image address randomization (ASLR). This broke ultrasn0w code naively using 0x1000 as the main executable base address. In addition to that, its FindReference function was using hardcoded offset/xref pairs for slidable images, which means every fw update will break it.
So, I've written a small dylib that works around those issues.
https://github.com/msftguy/ultrasn0w-fixer

Only tested on 3GS; will require changes for next betas.

On bluetooth in 4.0

• Bluetooth in 4.0 has a couple of new profiles: HID (meh) and.. Braille. Wait, what's exciting about Braille? Two things:
• It is one of the three services that call OpenSerialPort()
• It is the only one of them that isn't handled by OS isn't generally handled by the OS, unless you enable some obscure accessibility feature, unlike WiAP and Nike sensor profiles, meaning there are no side effects to connecting the service to arbitrary BT devices with serial profile.
  
  
  

Working iPhone recovery ramdisk with SSH ;-)

This information is deprecated; please use the new automatic tool here.

Fixing Blacksn0w on 3.1.3

Update: Ultrasn0w now supports 05.11 thru 05.13 with a new exploit that should fix all possible WiFi issues and any OS 4.0 problems. http://ultrasn0w.com/

Asking for it..

Pseudo-code:

VerifyLicense()
{
    char
         readbuf[16],
         plaintext[16],
         uuid[32]; 
    int hLic = open(LICENSE_FILE);
    get_uuid(uuid);
    read(hLic, readbuf, 16);
    raw_decrypt(readbuf, plaintext);
    memcmp(plaintext, uuid, 16);
}

Where raw_decrypt is an AES symmetric cypher function -)

Even more amazingly, raw_encrypt function is ALSO present in the code!

Troubleshooting 802.1x on the iPhone

• Create /private/var/preferences/SystemConfiguration/com.apple.eapolclient.plist with following contents:

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>LogFlags</key> <integer>255</integer> </dict> </plist>

• Log is in /var/log/eapolclient.en0.log

Tools: IDA 5.2 (talk about overkill..), iPhoneList

Snipping Tool on Server 2008 - no love?

Short:

Problem: Snipping Tool from Vista SKUs does not start on Server 2008 Solution:

1. Create a new directory, SnipTool
2. Copy System32\SnippingTool.exe to SnipTool
3. Copy System32\en-US\SnippingTool.exe.mui to SnipTool\en-US
4. Create a file called SnippingTool.exe.local in SnipTool directory.
5. Download this Zip file
6. Extract the contents of the Zip file, copy slc/x86/slc.dll to SnipTool directory (replace x86 with x64 on a 64-bit OS).

Befriending Live Mesh and Server 2008

Update: recent versions of Live Mesh do not perform this check any more

Tip of the day: Sony Rolly Motion Editor installation on English OS

Well, It looks like Rolly isn't popular enough here in States, so the only kind of forum posts I found recommended using a Japanese XP in VMware. Which is fine, except I've got no Japanese XP. After changing system locale failed to affect installer's behavior, next idea was to install a MUI. (Un?)fortunately for me and my remaining diskspace, Japanese MUI for x64 Vista SP1 failed to install, and I had to resort to other ideas. Such as: Tried to decrypt the setup.inx and decompile it with SID And figured that installer wants GetSystemDefaultUILanguage to return 0x411 (Japanese LCID) Step-by step instructions: 1. Run installer under debugger ntsd setup.exe in ntsd console, type:

sxi av a GetSystemDefaultUILanguage mov eax,411 ret g

2. Click next-next-..finish. Update: Batch file for lazy ones. Copy Motion Editor directory to the local disk, place this file inside and run it. Additional software: Rolly needs SonicStage in addition for Motion Editor. Fortunately for all non-Japanese speakers out there, there is an English version of that here. PS. You may also want to install 'support for East Asian languages' in Control Panel/Regional & Language Settings to prevent Japanese characters looking like boxes.