On 1/21/25 12:57 PM, some-java-user-99206970363698485...@vodafonemail.de
wrote:
It seems I wasn't informed that the report had been created; at
least I cannot find the confirmation mail for it. Note that I had
specified a different private contact e-mail address.
It's because the bug isn't
It seems I wasn't informed that the report had been created; at least
I cannot find the confirmation mail for it. Note that I had specified
a different private contact e-mail address.
It's because the bug isn't public.
... but I am the reporter!? It could of course be that there was an
attemp
Hello,
in JDK 9 the behavior of the JDWP socket connector was changed to only
allow local connections by default [1]. This was likely done for two
reasons:
1. In earlier versions JDWP would also listen for external connections
by default
2. When JDWP is exposed externally it represents a b
On 20/01/2025 20:07, some-java-user-99206970363698485...@vodafonemail.de
wrote:
:
Therefore I think it would be good if the JDWP connector, when `*`
(and maybe `0.0.0.0`) is used, printed a big warning on console which
cannot be overlooked, telling the user that this might be insecure.
Pre
On 2025-01-20 20:36, some-java-user-99206970363698485...@vodafonemail.de
wrote:
Thanks for the information! Though I cannot see the report. Is it
still pending review / evaluation or was it made private to hide
information? Is it still open or was it resolved as "Won't fix" or
similar?
Yes, t
Hello,
Your bug report exists in JBS: https://bugs.openjdk.org/browse/JDK-8329414
On 2025-01-20 20:07, some-java-user-99206970363698485...@vodafonemail.de
wrote:
Side note: I am rather certain I had also reported this on the JDK bug
tracker through https://bugreport.java.com quite a while ago
