A lot of people are reporting issues with iTunes and iPhoto and the annoying “Allow/Deny” Firewall prompts.
In a Terminal window, try this:
$ codesign -v /Applications/iTunes.app
/Applications/iTunes.app: a sealed resource is missing or invalid
As an aside, I also checked my copy of iPhoto 9… same thing:
$ codesign -v /Applications/iPhoto.app/
/Applications/iPhoto.app/: a sealed resource is missing or invalid
If you want more information, use more -v flags…
$ codesign -vv /Applications/iPhoto.app/
/Applications/iPhoto.app/: a sealed resource is missing or invalid
/Applications/iPhoto.app/Contents/Resources/English.lproj/FSCalendarsMissingView.nib/keyedobjects.nib: resource added
/Applications/iPhoto.app/Contents/Resources/GSNoCalendar.png: resource added
/Applications/iPhoto.app/Contents/Resources/English.lproj/LocalPrintingCutSheet.nib/keyedobjects.nib: resource modified
Code signing is part of what Mac OS X uses for verifying applications that have rules in the firewall. If the applications signature is invalid, then the application will prompt for “approval” each time it opens as it does not match the signature it should have!
What you are supposed to get, if the application has all of it’s parts and is signed correctly is:
$ codesign -v /Applications/iTunes.app
/Applications/iTunes.app: valid on disk
/Applications/iTunes.app: satisfies its Designated Requirement
The solution is to download and install the standalone installer version of iTunes.
I have just done that on my MacBook Pro and all is good with the world as far as iTunes is concerned… not quite so lucky with iPhoto as yet! That may require Apple to step-up!
Update: I have updated two different Macs in the past hour using Software Update and both instances of iTunes are correctly signed… it may have been resolved by Apple.
Update 2: I have just reinstalled iPhoto 9 and used the standalone download to upgrade it to 9.1, but the code-signing issues remains… over to you, Apple!