changed default SDK to the current one
fixed non-literal format string warning
project update caused by opening in XC4 I think
added xc4 workspace
added xc4 workspace
Changes for Hype
Added an XPC service to deal with sandboxing.

This fixes #163. It requires that you copy the XPC service into your main application bundle in
Contents/XPCServices and runs the remove from quarantine step of copying the finish_installation
app as well as launching finish_installation app outside of the sandbox. Sparkle will function
exactly as it does now for applications that do not copy the XPC service into their application
bundle.
Merged latest from Andy's branch
Updated project settings.
Removed -fsingle-precision-constant flag which LLVM doesn't recognise
fixes for warnings thrown up by xcode 4.4 / llvm
xcode 4.4 project settings update
Merge branch 'master' of https://github.com/andymatuschak/Sparkle into integration
Merge remote-tracking branch 'wbyoung/master' into sandboxing
Fixes #48: Adopt standard code signing in favor of DSA signing

Thanks to Mattt Thompson (@mattt) for tag-team-ing this with me.

With this change, if your app deploys only to 10.6+, then you can
dispense altogether with the DSA signatures on future updates to your
application: just make sure the "to" version satisfies the "from"
version's Apple code signing requirements. Most of you are probably
already doing that, and if you're not, you should be anyway.

Specifically, Sparkle validates the designated requirement of the "from"
version against the "to" version. By default, as of this writing, that
means that the bundle identifiers must be the same, and that the leaf
certificate of the signature is the same. So if you keep code signing
your app with the same cert, Sparkle will Just Work without any
additional DSA signature nonsense for you to deal with.

Traditional Sparkle DSA signatures will still be honored.

This support has only been extended to updates to the main app bundle.
If you're updating some other bundle, you will have to use DSA signatures
to secure your updates in the future.

***IMPORTANT: previously, Sparkle considered an update "safe" if both the
appcast and update were distributed over https. That is nowhere near as
strong a verification measure as code signing or the old-school DSA
signatures, so with this change, support for unsigned, https-distributed
updates has been removed. If you're targeting 10.6+, start code-signing
your apps if you haven't already, and everything will be fine. If you're
targeting earlier OS Xs, you'll need to start adding DSA signatures to
your appcasts. When you link this changed version of Sparkle into your
app, it will warn you on launch if you are not code signed and do not
have a DSA public key specified in your Info.plist.
Making sure to initialize all Security types
Added kSecCSCheckAllArchitectures to the flags for code signing validation so that inactive architecture binaries are checked as well in the update.
Fixed potential crasher in code signing in the case that the host application is not code signed.
Merge branch 'master' into CodeSigning
Disable row selection in the system profile table by implementing the table delegate and turning off "Avoid Empty Selection", "Preserve Selection" and "Select Inserted Objects" on the array controller in the nib.
Merge in changes for sandboxing and XPC

Pull request here: https://github.com/andymatuschak/Sparkle/pull/165
Changes here: https://github.com/wbyoung/Sparkle/commit/dbd2b9b30aad66296fab5cf9b980bf02020fa71a