-
Enhancement
-
Resolution: Fixed
-
P3
-
11, 14, 15
-
b11
-
os_x
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8240835 | 14.0.2 | René Schünemann | P3 | Resolved | Fixed | b01 |
| JDK-8247349 | 13.0.4 | René Schünemann | P3 | Resolved | Fixed | b05 |
| JDK-8239820 | 11.0.7 | René Schünemann | P3 | Resolved | Fixed | b05 |
Currently when a certificate is present, all executables and libraries are being signed. For Apple notarization to work properly, the whole bundle in its final form must bee deep signed.
The bundle directories which are created within the images directory (images/jdk-bundle, images/jre-bundle) cannot be used for signing the bundle, because some files and folders are getting removed before creating the archive file.
There needs to be an intermediate step after the creation of the bundle directory in images and creating the archive, where the bundle is present on disk in its final form, which then can be signed.
The bundle directories which are created within the images directory (images/jdk-bundle, images/jre-bundle) cannot be used for signing the bundle, because some files and folders are getting removed before creating the archive file.
There needs to be an intermediate step after the creation of the bundle directory in images and creating the archive, where the bundle is present on disk in its final form, which then can be signed.
- backported by
-
JDK-8239820 Deep sign macOS bundles before bundle archive is being created
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8238225 Issues reported after replacing symlink at Contents/MacOS/libjli.dylib with binary
-
- Resolved
-
-
-
- Resolved
-