For people with 10.5.6, you're going to have to re-enable DFU mode in order to run Jailbreak. The Dev Team blog has instructions on how to do that, but after you're done, you should disable DFU mode by running the steps backwards, as we documented here. It may screw up your machine if you don't. [iPhone Dev]

Yes, all we have here is an annotated hour-long PowerPoint, and yes, almost all of the content is of interest only to the actual haxxors that gathered at 25C3 to watch, but for me, it's a thrill to hear these guys talk about the software that we've covered and used ourselves for so long. It's also a thrill to hear little tidbits like the 180 IP addresses inside apple that the Dev Team guys have tracked as frequent updaters of Pwnage and Quickpwn.

Up until this weekend in Berlin, most of the iPhone Dev Team had never met each other in person. And I only wish we could have gotten a quick camera pan over to the guys identified as the team members who wish to remain anonymous—in the corner, wearing "PwnApple" t-shirts, speaking Russian. [hackaday via BBG]

The update prevents jailbreaking by disabling the software at the computer level, a step up from what the company usually does: release a firmware update that re-locks the iPhone. Now it's stopping your Mac from recognizing the device in DFU (device firmware update) mode by inflicting new code on the USB ports on Apple computers.

While the iPhone Dev Team is no doubt working to figure out a new hack around this, some are reporting that the simplest way to work around the update for now is to copy some of the 10.5.5 framework files over the newer ones... or not update. [Information Week and Spaziocellulare]

It's a very specific problem, too — the tool still runs, and users who have a pre-modified firmware created on another Mac or Windows machine are able to 'restore' their devices to a jailbroken state without any trouble. It's the creation of modified firmware, which is the central purpose of the Pwnage tool, that has been kneecapped.

Though the hardware is where one sees the most conspicuous changes in the new MacBook, this problem most likely stems from a subtle software modification. It's not clear what specifically changed, but a new build of iTunes, unique to the new MacBooks, seems like a likely culprit. Of course, this news comes just after we're once again reminded of the App Store's awesome competition-busting rules. Your move, Dev Team. [Howard and iPodTouchFans — Thanks, Charles]

The nice thing about iTunes decisions is that we can provide you with patches to counter them. We have one such patch already for Mac iTunes 8 for iPod touch. We’ll be working out the full suite of patches for all the combinations over the next week.

Begun the Apple-Hackers iTunes Wars have. [iPhone Dev Team Blog]

You can download the new WinPwn at this direct link, and pick up a torrent for QuicPwn Tool for Mac here.
[WinPwn and Dev Team - Thanks, Estevan and Jason]

According to their site, WinPwn 2.0.0.1 has the following features:

- Support for both 1.1.4 and 2.0

- Custom Image Support

- Custom Payload Support

- 3g iPhone support

[WinPwn and Rapidshare Mirror]

- It auto-finds the bl39 and bl46 files better, if they’re on your computer.
- It creates the ~/Library/iTunes/Device Support/ folder if not present, which should help with some 1600 errors people have been having.
- Many people have reported the PwnageTool not starting up at all (the icon never stops bouncing). This issue should be resolved now.
- The Sparkle AppCast URL is fixed in this version, so automatic updates should work for future releases.

If you successfully jailbroke and unlocked your iPhone with OS 2.0 with the previous one, there's no need for you to use this version. Otherwise, you can download from here or here.

We can't wait for the tool to be released. [iPhone Dev Blog]

You can download from here and here.

If you were wondering how I was doing push email tests on iPhone OS 2.0 and Vodafone UK, this is the reason why. The code wizard commandos at the iPhone Dev Team have been working on this non-stop since the early days of beta testing. In fact, I had iPhone OS 2.0 running on my iPhone since last week. That was version 5A345, two below 5A347, but identical in functionality.

Now that the official iPhone OS 2.0 is out, the iPhone Dev Team will release their Pwnage tool for everyone to unlock and jailbreak their iPhones soon, although the specific date/time is not firm yet. It may not be as interesting as before—since most countries now have the iPhone and it will be impossible to buy without doing a contract first—but people looking to install unsigned applications and buy pay-as-you-go cards while traveling—instead of roaming—will find it very useful.

And besides, we don't get tired of seeing the Death Star exploding again and again. [iPhone Dev Team Portal]

Apart from the previous unlocking and jailbreaking, the new version has three main features:

• Easily customizable images for start and restore screens.
• You can use packages to customize your firmware and install software right away, on one single update.
• You can now pwn iPhone 1.2.0 beta 3.

We also got confirmation of what we already hinted last week: Apple is preparing up to battle the hackers, with more and more code running signed and secured inside the iPhone. This will make things more difficult for the iPhone Dev Team.

How much more difficult? Would this be a real challenge to the iPhone Dev Team's current dominance in the hacking war? According to them, it may be. But it just makes things more interesting and fun, which is exactly what we wanted to hear.

Get your update now. [iPhone Dev Team via Pwnage in Gizmodo]