I have pretty much totally moved away from the entire Jailbrake scene.
In fact out of all 6 devices I own only 1 is Jailbroken and I only keep that one on hand because I have 2 paid apps that I released back during firmware 1.x and before the AppStore.

I am very sorry if this news comes as a disappointment.

Since 2.0 and the AppStore came out Jailbraking has lost its appeal to me as I use AT&T so that’s not a concern for me and since the only reason I ever got into the Jailbrake scene in the first place was to be able to write my own apps and run other peoples apps on a great device that had so much more potential.

Now with the AppStore it seems like Jailbraking is done for one or more of the following: Carrier Unlock, Apps that Apple won’t approve, and Warez.
I don’t care about carrier unlocks, and I don’t approve of Warez (even if you say you use them as demo’s and buy the ones you like, because 99.9% are not doing that), and that just leaves apps that Apple won’t approve. This would be the only thing to keep me around but Apple lets most things in (it might take a couple rejections first though) that I am interested in.

Also, Apple has been getting really good at closing all the holes that made this app possible (as technically they are security holes).
So much so that the last version “oddly” wouldn’t work for everyone, including me.
I spent a ton of time searching for new ways back then and never found anything that I was happy with, and then I finally gave up and just stopped syncing my work email.

(It was a plus for my day job to have me accessible by email all the time and I decided it wasn’t worth the time and work I was putting into not having my personal device locked down)

Of course I understand that this isn’t the same for everyone.
All I can really say is I feel your pain (as if that helps anything), and that in a comment on the post way back about version 3.0 of KillExchangeLocks, Eirik mentioned that a new app has just shown up in Cydia called: “Exchange Unlock”.

With that in mind, let me get the “legalize” (if you will) out of the way.
“Exchange Unlock” is not my work, nor do I have anything to do with it in any way.
I have NO idea if it works, and I can not be held responsible if it blows up your device, literally or figuratively.

I do wish you the best of luck, and encourage you to check out my other work at: HashBang Industries (http://www.HashBangInd.com)

The fix that broke things was CVE-ID: CVE-2008-4229

Impact: Restoring a device from backup may not re-enable the Passcode Lock

Description: The Passcode Lock feature is designed to prevent applications from being launched unless the correct passcode is entered. A race condition in the handling of device settings may cause the Passcode Lock to be removed when the device is restored from backup. This may allow a person with physical access to the device to launch applications without the passcode. This update addresses the issue by improving the system’s ability to recognize missing preferences. This issue does not affect systems prior to iPhone OS 2.0 or iPhone OS for iPod touch 2.0. Credit to Nolen Scaife for reporting this issue.

http://lists.apple.com/archives/security-announce/2008/Nov/msg00002.html

The key parts here is the resoultion, “This update addresses the issue by improving the system’s ability to recognize missing preferences”, and the person to blame is Nolen Scaife for reporting this issue.

KillExchangeLocks version 3 does not implement the ideal solution as Apple has done a pretty good job on their fix. Instead of removing the passcode automatically like before, instead you now force the settings app to alow you to remove the passcode, as if you had setup a passcode without using Exchange.

This still times out every 24 hours like before, as Apple is actively querying the Exchange server every 24 hours to update and/or validate the security settings.

The up side is you should only have to run this part once, and you will always be able to remove the passcode.

Version 3 gives you the option if you want to modify your Auto Lock timeout.

The problem here is that the iPhone will over write any change if you go into the Settings app and click on the General tab (which shows your timeout setting).

Therefore this could need to be reset often, if you go into Settings -> General a lot.

I added some extra Time out levels for your convience.

You can now choose between: Never, 1 min, 2 min, 3 min, 4 min, 5 min, 10 min, 15 min, 20 min, 25 min, 30 min, 35 min, 40 min, 45 min, 50 min, 55 min, and 1 hour time out levels.

As I said before, this is by no means the ideal fix, but it is the only way I have found so far, and I figure this is better then having nothing.

If you really want a better fix in place, I would ask you to think about donating to this project as that would make it easier for me to work on this project then other paying projects. It is in no way required, but welcomed. If you wish to donate you can do so using PayPal.

KillExchangeLocks is available in Cydia under Utilities.

It will be going out to testers in the next couple of days and should be out for the world very soon.

If you just can’t wait and wan’t to help beta test, email me and we will see what we can do.

This version features a VERY basic UI so users know the program has actually started.
It also removes the restrictions on the auto-lock feature, so users can use the normal settings section to choose their preferred auto-lock time.

The big news of 1.1 is that for *some* users, they should only have to run the app 1 time, as we trick the iPhone into thinking a passcode is not needed, and therefore it will not ask you every day. I say *some* because from testing, this currently only works for certain exchange setups.

http://codegenocide.com/KillExchangeLocks.zip

I had RemindYou 80% ported to 2.0, compiling directly on the iphone (as that is the only working toolchain right now) but then I installed something off of Cydia today and when I left Cydia my iPhone was frozen.

I let it sit for 5 minutes and nothing.
So I rebooted and I am stuck at the Apple logo.
I have rebooted 10 times and let it sit at the apple logo for over an hour.

MY IPHONE IS BRICKED!!!

As it was iTunes would not even see it.

Luckily I was able to force it into restore mode and then iTunes found it.

So I was able to get it reinstalled, but since I was working directly on the iPhone all of my work to port RemindYou was lost!

I am sure you are asking why were you not using SVN or something…

Well I have the project in Mercurial, but native on the iPhone is only SVN and Git, not Mercurial, so I wasn’t able to publish my changes.