-
Bug
-
Resolution: Obsolete
-
High
-
None
-
5.5.1, 5.6.0, 5.7.1
Problem
- Mac OS X requires binaries to be signed with a Developer ID certificate to run out of the box on mac os x. Without code signing, you should get a warning that the app isn't from the App Store or a registered Apple Developer.
- This used not to be a problem as users were told how to fix it
- Latest versions of Mac OS X report that the download is corrupted rather than blocked by developer id. This is an apple bug. Getting to them to fix it will be near impossible.
Possible solution
- We get a Developer ID certificate and sign our installer binary with it. This is easy to get - we have one for HipChat and we can generate another one.
- Make code signing work
- We use the command line tool to resign each binary after install4j has packaged it (mac only). This would require us to package it manually as a DMG not preferred
- Upgrade to the latest install4j 5.x and use its built in code signing to sign the developer id certificate. This should work on all platforms and be automated preferred
- duplicates
-
-
- Closed
-
- mentioned in
-
![[Atlassian Documentation] Page](/images/icons/generic_link_16.png "[Atlassian Documentation] Page")
Page
No Confluence page found with the given URL.
-
Page
No Confluence page found with the given URL.
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
- was cloned as
-
[BAM-11742] Installer package is "damaged and cannot be reopened" on Mac OS X
The problem is back in Bamboo 5.5.1. Mac installer package is damaged. Please check the attached screenshot.
Please refer to the following KB article for a workaround:
Another installation option is to download the "Bamboo 5.5.1 - TAR.GZ Archive" package instead and extract it under <bamboo-installation-directory>. Then editing "bamboo-init.properties" file under <bamboo-installation-directory>/atlassian-bamboo/WEB-INF/classes to point at the correct <bamboo-home-directory> before running Bamboo.
The appropriate certificate is now being used to sign the DMG.
Just downloaded Bamboo 5.6: "atlassian-bamboo-5.6.0.dmg" and noticed that this problem still exists with the MAC installer package. Please see the attached screenshots.