-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Description
What steps will reproduce the problem?
1. Go to System Preferences > Security & Privacy > General
2. Change the option to either "Mac App Store" or "Mac App Store and identified
developers".
3. Close the Security & Privacy window.
4. Download the DMG file and install Jarzilla.
5. Right-click the Jarzilla icon, hold down Command, and click Open (this is
necessary to override the security setting the first time you run the
application.)
What is the expected output?
OSX should prompt you to confirm you want to open the application despite
having the aforementioned security setting turned on. You click Open and the
app should launch.
What do you see instead?
OSX presents a dialog that says "'Jarzilla' is damaged and can't be opened.
You should move it to the Trash." with a "Cancel" and "Move to Trash" button.
The Console application shows the following:
4/16/14 3:42:32.496 PM CoreServicesUIAgent[21855]: Error SecAssessmentCreate:
The operation couldn’t be completed. (OSStatus error -67030.)
What version of the product are you using? On what operating system?
0.1.5. OSX Mavericks 10.9.2
Please provide any additional information below.
I verified the SHA-1 sum of the DMG file matches what is on the website, so
it's definitely not corrupt.
As a workaround, if you like keeping the security setting turned on in System
Preferences:
1. Go to System Preferences > Security & Privacy > General
2. Change the option to "Anywhere".
3. Close the Security & Privacy window.
4. Download the DMG file and install Jarzilla.
5. Run Jarzilla. OSX will still warn you: "'Jarzilla' is an application
downloaded from the Internet. Are you sure you want to open it?"
6. Click Open.
7. Go to System Preferences > Security & Privacy > General
8. Change the option back to either "Mac App Store" or "Mac App Store and
identified developers" (whichever you prefer).
Since the application was opened once while the security check was disabled, it
won't run the security check again.
Original issue reported on code.google.com by Motionbl...@gmail.com on 16 Apr 2014 at 8:30