search

machawk1 / wail

:whale2: Web Archiving Integration Layer: One-Click User Instigated Preservation
https://matkelly.com/wail
MIT License
351 stars 35 forks source link

OS X GateKeeper prevents WAIL from opening due to not being through the app store #59

Open machawk1 opened 10 years ago

machawk1 commented 10 years ago

Error encountered: "WAIL" can't be opened because it is from an unidentified developer. Your security preferences allow installation of only apps from the Mac App Store and identified developers.

This approach I have seen other developers take is to instruct the user to allow unauthorized apps. Reading through the App Store rules, it's unlikely WAIL would be accepted because it contains application/executable within (e.g., Heritrix).

Is it possible to become an "identified" developer without being limited to the App Store?

machawk1 commented 10 years ago

Three Options in "System Preferences > Allow apps downloaded from" are Mac App Store Mac App Store and identified developers (default) Anywhere

machawk1 commented 10 years ago

Similar to #48 Relevant: http://www.intransitione.com/blog/take-java-to-app-store/

machawk1 commented 10 years ago

Bumping this to Future Release, as it's not a priority to distribute WAIL through the appstore.

machawk1 commented 8 years ago

screen shot 2016-01-22 at 7 42 57 am

machawk1 commented 8 years ago

https://github.com/pyinstaller/pyinstaller/wiki/Recipe-OSX-Code-Signing

The codesigning process can likely be added to the "MAKEFILE" though this seems to defeat the purpose of codesigning.

machawk1 commented 8 years ago

Using codesign results in the error unsealed contents present in the bundle root due to the additional directories within WAIL.app that are abnormal for .app's (e.g., archives, archiveIndexes, bundledApps, etc). This is new as of OS X 10.9.5.

machawk1 commented 7 months ago

The entitlement can also be passed to pyinstaller to facilitate app signing, see https://forums.developer.apple.com/forums/thread/695989