Permalink
Commits on Dec 7, 2012
  1. Merge remote-tracking branch 'blackpixel/warnings-pull-request'

    andymatuschak committed Dec 7, 2012
    Conflicts:
    	th.lproj/Sparkle.strings
Commits on Dec 6, 2012
  1. Fixed warnings in xibs, switched to lldb and fixed occasional copy ph…

    rustle committed Dec 6, 2012
    …ase error from incorrect text encoding
Commits on Nov 20, 2012
  1. Merge branch 'CodeSigning'

    andymatuschak committed Nov 20, 2012
Commits on Nov 16, 2012
  1. Merge pull request #210 from kainjow/master

    andymatuschak committed Nov 16, 2012
    Disable row selection in system profile table
  2. Fixes #222: Long version ids (12 digits based on reverse date) cause …

    andymatuschak committed Nov 16, 2012
    …update to work no longer
  3. Fixed unit tests for 10.8

    andymatuschak committed Nov 16, 2012
Commits on Nov 13, 2012
Commits on Nov 10, 2012
  1. Update strings files to standardize ellipsis character (…) instead of…

    Ryan Maxwell committed Nov 10, 2012
    … three dots (…)
    
    Also change don't to curly quote don’t in dialog.
Commits on Sep 13, 2012
Commits on Sep 5, 2012
  1. Disable row selection in the system profile table by implementing the…

    kainjow committed with Kevin Wojniak Sep 5, 2012
    … table delegate and turning off "Avoid Empty Selection", "Preserve Selection" and "Select Inserted Objects" on the array controller in the nib.
Commits on Aug 17, 2012
  1. Fixes #198: Problem with 10.5

    andymatuschak committed Aug 17, 2012
    Implicitly linking the Obj-C runtime with the 10.7 SDK is causing us to
    inadvertently reference libblocks symbols, which don't exist prior to
    10.6.
Commits on Aug 16, 2012
  1. Fixes #133: Sparkle deleting/replacing the wrong executable when it u…

    andymatuschak committed Aug 16, 2012
    …npacks
    
    -[SUHost installationPath] can return different values before and after
    the installation is performed, because it may attempt to normalize the
    installation path--but only if the normalized version of the path isn't
    already present. Which it would be after the installation had completed.
    
    Now we only compute the installation path once for the whole installation
    process.
Commits on Jul 27, 2012
Commits on Jul 26, 2012
  1. Add Thai localization

    Chotiwat Chawannakul committed Jul 26, 2012
Commits on Jul 24, 2012
  1. Fixed potential crasher in code signing in the case that the host app…

    andymatuschak committed Jul 24, 2012
    …lication is not code signed.
  2. Added kSecCSCheckAllArchitectures to the flags for code signing valid…

    andymatuschak committed Jul 24, 2012
    …ation so that inactive architecture binaries are checked as well in the update.
Commits on Jul 6, 2012
  1. Merge pull request #183 from sinbad/fix-10.6-arg-list-too-long

    andymatuschak committed Jul 6, 2012
    Use NSFileManager interface for DMG unarchive only for 10.7+.
Commits on Jul 5, 2012
  1. Fixes #48: Adopt standard code signing in favor of DSA signing

    andymatuschak committed Jul 5, 2012
    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.
Commits on Jul 4, 2012
  1. Delegated password prompting to the update driver.

    andymatuschak committed Jul 4, 2012
    The SUDiskImageUnarchiver shouldn't know about UI, and besides,
    it's important that update drivers which should not display UI (like
    the automatically-installing and probing drivers) should not display
    password prompts.
Commits on Jun 28, 2012
  1. Use NSFileManager interface for DMG unarchive only for 10.7+. On 10.6…

    sinbad committed Jun 28, 2012
    …, [NSFileManager copyItemAtPath:toPath:error:] can fail with "Argument list too long" if the app bundle contains too many files.
    
    The switch to NSFileManager was only required for 10.7 anyway, 10.6 always worked fine.
Commits on Jun 27, 2012
Commits on May 28, 2012
  1. Fixes #44: maximumSystemVersion key

    Stefan Hoffmann committed May 28, 2012