Integrity by Default
summary
Integrity by default means Java disables mechanisms that can break guarantees unless the application explicitly opts in; concrete offenders are deep reflection, unsafe and native access (JNI/FFM), plus agents and dynamic bytecode changes. Modules enforce strong encapsulation since JDK16, unsafe methods are deprecated for removal and JDK24 surfaces warnings, while opt‑ins use flags like add‑opens or --enable-native-access. The claim: application owners — not libraries — must accept the risk and migrate code or supply explicit permissions.
AI-written summary · about
chapters (5)
- 0:00Intro
- 1:39Integrity and its Importance
- 8:23Mechanism that can Undermine Integrity
- 10:02Integrity by Default and Intentional Risk
- 17:07Progress Toward Integrity by Default
related talks
51mJava - Integrity by Default
42mHidden security features of the JVM - everything you didn’t know and more
48mHidden Security Features of the JVM - Everything You Didn’t Know and More
47mJDK 9, 10, and 11: Pitfalls for the Unwary
43mSecurity Architecture of the Java Platform
26mFinding Alternatives to Security Manager
46mModular Development with JDK 9 and Beyond
44mJava Code Security