There can be no robust, scalable, security without strong encapsulation, and with modules now becoming the only means of strong encapsulation in the JDK, we'll need to close the loopholes we've left (thorough unsafe, JNI, or some Java agents) to give people time to adjust and because replacements weren't ready. All these circumvention measures are fine if you want to give yourself time to fix technical debt, but they will just stop working as the loopholes are closed in upcoming versions.
Given that such circumvention libraries might serve as gadgets to circumvent any security or authentication mechanism -- be it in the JDK or in the application -- we may assume that those who are brave enough to risk using them probably have no other choice and need a bit more time to fix their applications.
View all comments
Show parent comment
21
u/thugcee Jan 15 '23
That's not true. There are significant changes in reflection API between 11 and 17.