[jira] [Resolved] (DIRSTUDIO-1140) Apple Sierra shows corrupted app when launching Studio
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSTUDIO-1140. Resolution: Fixed Let's hope this is fixed now by signing the app: https://github.com/apache/directory-studio/commit/59948821d6b002ffbe47f3a4038d07610f14ceaf > Apple Sierra shows corrupted app when launching Studio > -- > > Key: DIRSTUDIO-1140 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1140 > Project: Directory Studio > Issue Type: Bug > Components: studio-apacheds >Affects Versions: 2.0.0-M12 >Reporter: Brian Wright >Assignee: Stefan Seelmann >Priority: Major > Fix For: 2.0.0-M14, 2.0.0-M13 > > Attachments: ADS-Damaged.png > > > After downloading and launching Apache Directory Studio 2.0.0 M12 on MacOS X > Sierra, I am presented with a panel that says: > {quote}"ApacheDirectoryStudio.app" is damaged and can't be opened. You should > move it to the Trash.{quote} > The cause of this issue is because of Sierra's enhanced security related > to... {{resource fork, Finder information, or similar detritus not allowed}} > and code signing. > This may or may not be related to code signing specifically, but is more > likely related to the version of Xcode used to create this app version. > Here's the security issue: > {quote}This is a security hardening change that was introduced with iOS 10, > macOS Sierra, watchOS 3, and tvOS 10. > Code signing no longer allows any file in an app bundle to have an extended > attribute containing a resource fork or Finder info.{quote} > To find the offending attributes, use: > {code}xattr -lr /Applications/ApacheDirectoryStudio.app{code} > To fix the app and allow it to function, these attributes *must* be stripped > with: > {code}xattr -cr /Applications/ApacheDirectoryStudio.app{code} > Better, the next time someone compiles the app for release on MacOS X, make > sure it doesn't include these offending attributes. I would assume the latest > version of Xcode should prevent the creation of these attributes. If not, > then the app should be stripped with {{xattr}} before package and release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (DIRSTUDIO-1140) Apple Sierra shows corrupted app when launching Studio
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSTUDIO-1140. Resolution: Fixed Fix Version/s: 2.0.0-M13 > Apple Sierra shows corrupted app when launching Studio > -- > > Key: DIRSTUDIO-1140 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1140 > Project: Directory Studio > Issue Type: Bug > Components: studio-apacheds >Affects Versions: 2.0.0-M12 >Reporter: Brian Wright > Fix For: 2.0.0-M13 > > Attachments: ADS-Damaged.png > > > After downloading and launching Apache Directory Studio 2.0.0 M12 on MacOS X > Sierra, I am presented with a panel that says: > {quote}"ApacheDirectoryStudio.app" is damaged and can't be opened. You should > move it to the Trash.{quote} > The cause of this issue is because of Sierra's enhanced security related > to... {{resource fork, Finder information, or similar detritus not allowed}} > and code signing. > This may or may not be related to code signing specifically, but is more > likely related to the version of Xcode used to create this app version. > Here's the security issue: > {quote}This is a security hardening change that was introduced with iOS 10, > macOS Sierra, watchOS 3, and tvOS 10. > Code signing no longer allows any file in an app bundle to have an extended > attribute containing a resource fork or Finder info.{quote} > To find the offending attributes, use: > {code}xattr -lr /Applications/ApacheDirectoryStudio.app{code} > To fix the app and allow it to function, these attributes *must* be stripped > with: > {code}xattr -cr /Applications/ApacheDirectoryStudio.app{code} > Better, the next time someone compiles the app for release on MacOS X, make > sure it doesn't include these offending attributes. I would assume the latest > version of Xcode should prevent the creation of these attributes. If not, > then the app should be stripped with {{xattr}} before package and release. -- This message was sent by Atlassian JIRA (v6.4.14#64029)