Re: [External] : Re: JEP draft: Disallow the Dynamic Loading of Agents by Default

2023-04-30 Thread Bernd
If you keep instrumentation (and i don’t think you want to remove it), don’t make it harder to use programmatically… that really does not make much sense. And please don’t add captcha-like mechanism that’s ridiculous. Backport the fix to turn it off, I will be the first to

Re: [External] : Re: JEP draft: Disallow the Dynamic Loading of Agents by Default

2023-04-30 Thread Ron Pressler
Hi Mike! On 30 Apr 2023, at 19:59, Mike Hearn mailto:m...@plan99.net>> wrote: we’ve begun to explore means other than the flag to allow a tool to load an agent at runtime How about restricting access to the jcmd socket. For in-VM code it can be blocked at the filesystem implementation level, a

Re: [External] : Re: JEP draft: Disallow the Dynamic Loading of Agents by Default

2023-04-30 Thread Mike Hearn
> we’ve begun to explore means other than the flag to allow a tool to load an > agent at runtime How about restricting access to the jcmd socket. For in-VM code it can be blocked at the filesystem implementation level, and for sub-processes by using the operating system APIs to determine if the o

Re: [External] : Re: JEP draft: Disallow the Dynamic Loading of Agents by Default

2023-04-30 Thread Ron Pressler
Hi Dan! > On 29 Apr 2023, at 03:30, Dan Heidinga wrote: > > Hi Ron, > > Thanks for writing up the JEP draft outlining the proposal to disallow > dynamic loading of agents by default. The Red Hat Java team has continued to > discuss this proposal internally and with our stakeholders. > > Whi