installer_directory variable on Sierra OSX

Comments

4 comments

  • Avatar
    Guy Linksman

    Debug file sent :) thanks

    0
    Comment actions Permalink
  • Avatar
    Mayank

    @BitRock Support

    Hi Guys,

    I am also facing the same issue. Can you please provide estimate till when you will be able to provide solution for the same.

    0
    Comment actions Permalink
  • Avatar
    michiel

    macOS Sierra introduces a security feature that prevents digitally signed applications downloaded from the internet from accessing unsigned resources

    https://developer.apple.com/library/content/releasenotes/MacOSX/WhatsNewInOSX/Articles/OSXv10.html

    Starting in macOS 10.12, you can no longer provide external code or data alongside your code-signed app in a zip archive or unsigned disk image. An app distributed outside the Mac App Store runs from a randomized path when it is launched and so cannot access such external resources. To provide secure execution, code sign your disk image itself using the codesign tool, or distribute your app through the Mac App Store. For more information, see the updated revision to macOS Code Signing In Depth.

    So it seems one option is to distribute all contents in the installer itself - for example not reference any files using the ${installer_directory} variable.

    Another option is to sign the final DMG file as well so that the application is run from within this DMG file and is not copied to randomized, temporary directory.

    0
    Comment actions Permalink
  • Avatar
    Guy Linksman

    Thanks for the info, I'll try these two options.

    0
    Comment actions Permalink

Please sign in to leave a comment.