directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Seelmann (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRSTUDIO-1140) Apple Sierra shows corrupted app when launching Studio
Date Sun, 03 Sep 2017 18:30:00 GMT

    [ https://issues.apache.org/jira/browse/DIRSTUDIO-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16151901#comment-16151901
] 

Stefan Seelmann commented on DIRSTUDIO-1140:
--------------------------------------------

Fixed: http://svn.apache.org/viewvc?rev=1807158&view=rev

It's not related to Eclipse version which creates the app without offending attributes, but
the way we build the DMG: {{hdiutil makehybrid -hfs-openfolder}} creates those extended attributes.
I found another way at https://porkrind.org/missives/mac-os-x-codesigning-woes/

Note: I only have an old 2009 Macbook which I cannot upgrade to Sierra so I cannot fully verify,
but {{xattr -lr}} no longer shows the "com.apple.FinderInfo" attributes.

> 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)

Mime
View raw message