[External] : Re: New candidate JEP: 451: Prepare to Disallow the Dynamic Loading of Agents

Kirk Pepperdine kirk.pepperdine at gmail.com
Thu May 18 22:52:12 UTC 2023



> On May 18, 2023, at 2:55 PM, Ron Pressler <ron.pressler at oracle.com> wrote:
> 
> 
>> On 18 May 2023, at 21:45, Kirk Pepperdine <kirk.pepperdine at gmail.com> wrote:
>> 
>> Hi Ron,
>> 
>> And in that JEP there is...
>> 
>> "To attain our goal of integrity by default, we will gradually restrict these APIs and close all loopholes in a series of upcoming JEPs, ensuring that no library can assume superpowers without the application's consent. Libraries that rely on these APIs should spend the time remaining until they are restricted to prepare their users for any necessary changes”.
>> 
>> It is these types of statements in that JEP that are adding to my confusion. What is being restricted? Where and how is that restriction being enforced given that it can apparently be turned on?
> 
> By “restricted” we mean “disallowed by default unless the application allows it.” We try to use that terminology consistently. In this JEP we’re just “preparing to restrict”, which means that unless explicitly allowed by the flag, there will only be a warning.

Understood… but the question remains. If I understand this correctly, the API in question java.lang.instrument.Instrumentation. What in that API would be restricted? Are there other APIs that might be affected?


Kind regards,
Kirk



More information about the serviceability-dev mailing list