-
Enhancement
-
Resolution: Fixed
-
P3
-
20
-
b16
-
os_x
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8294996 | 17.0.6-oracle | Erik Joelsson | P3 | Resolved | Fixed | b02 |
JDK-8298036 | 17.0.6 | Dukebot | P3 | Resolved | Fixed | b06 |
JDK-8296264 | 11.0.19-oracle | Erik Joelsson | P3 | Resolved | Fixed | b01 |
JDK-8302653 | 11.0.19 | Christoph Langer | P3 | Resolved | Fixed | b03 |
There is a special entitlement "com.apple.security.get-task-allow" which is needed to be able to get core dumps. Xcode will automatically set this on debug builds, but not on release builds. We never include this as it's not allowed when notarizing applications.
I was recently made aware of the possibility of adding entitlements without actually signing a binary. This makes it possible for us to add the get-task-allow entitlement to builds that are never intended to be notarized. We can also be consistent with adding the standard set of entitlements to all builds, regardless of if proper signing is going to be performed.
Not adding any entitlements to non signed builds is currently not a problem on x64, however, on aarch64, the Xcode linker will unconditionally always perform an "adhoc" signing without any entitlements. This is blocking at least core file generation from those binaries, and probably other kinds of debug operations as well.
In this change, I propose that we by default always add entitlements to all builds, and as long as we aren't explicitly signing with a real signing identity with hardened runtime enabled, we should also add the get-task-allow entitlement.
- backported by
-
JDK-8294996 Optionally add get-task-allow entitlement to macos binaries
-
- Resolved
-
-
JDK-8296264 Optionally add get-task-allow entitlement to macos binaries
-
- Resolved
-
-
JDK-8298036 Optionally add get-task-allow entitlement to macos binaries
-
- Resolved
-
-
JDK-8302653 Optionally add get-task-allow entitlement to macos binaries
-
- Resolved
-
- blocks
-
JDK-8293563 [macos-aarch64] SA core file tests failing with sun.jvm.hotspot.oops.UnknownOopException
-
- Resolved
-
- relates to
-
JDK-8294310 compare.sh fails on macos after JDK-8293550
-
- Resolved
-
-
JDK-8300490 Spaces in name of MacOS Code Signing Identity are not correctly handled after JDK-8293550
-
- Resolved
-
-
JDK-8298343 "Could not confirm if TargetJDK is hardened." warning for SA tests on macosx-aarch64-debug
-
- Resolved
-
-
JDK-8293563 [macos-aarch64] SA core file tests failing with sun.jvm.hotspot.oops.UnknownOopException
-
- Resolved
-
-
JDK-8293965 Code signing warnings after JDK-8293550
-
- Resolved
-
- links to
-
Commit openjdk/jdk11u-dev/630c80eb
-
Commit openjdk/jdk17u-dev/da6fca4d
-
Commit openjdk/jdk/f42caefe
-
Review openjdk/jdk11u-dev/1739
-
Review openjdk/jdk17u-dev/916
-
Review openjdk/jdk/10275