[External] : Re: RFR: 8286850: [macos] Add support for signing user provided app image [v2]

[Michael Hall]

> On Jun 22, 2022, at 7:15 PM, Michael Hall <mik3hall at gmail.com> wrote:
> 
> 
> 
>> On Jun 22, 2022, at 6:57 PM, Alexander Matveev <alexander.matveev at oracle.com> wrote:
>> 
>> Hi Michael,
>> 
>> Did you modified app image after it was signed and before DMG was created? If yes, it is expected behavior and we will not sign app image when generating DMG.
>> 
>> Can you provide all steps you did to get to issue below?
>> 
>> Thanks,
>> Alexander
>> 
> Alexander,
> 
> They were pretty much as shown. 
> 1). Create with script shown.
> 	verify with previously shown error
> 2). Sign as per your post
> 	verify showed good
> 3). DMG as previously shown
> 	DMG created and opens
> Reported good
> Did verify against mounted dmg, got errors shown
> Copied to Applications directory, got errors shown.
> 
> No changes to application image or dmg done at any point. Nothing except codesign verifies.
> 
> Prior bug with same error appears to have not had a resolution. I wasn’t depending on successful code signing at the time I don’t think.
> JDK-8263156 : [macos]: OS X application signing concerns - a sealed resource is missing or invalid
> https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8263156
> 	
> The three steps to create - sign - dmg should be pretty easy to reproduce with a test app.
> 
> Mike
> 
That may of been when I was doing an incorrect copy to a test directory using ‘cp’. I had some errors that corrected when I switched to the OS/X ‘ditto’ command.
How are you copying to the dmg for step 3? Possibly something happens there?