Re: InetAddress API extension proposal

2024-03-28 Thread Sergey Chernyshev
Hi Alan, Thank you for your comments! I will post this to net-nev too as you suggested. Am 28.03.24 um 00:23 schrieb Alan Bateman: On 27/03/2024 17:05, Sergey Chernyshev wrote: In the discussion of .ofLiteral() it was not concluded that .ofPosixLiteral() would be insecure or undesirable

Re: InetAddress API extension proposal

2024-03-27 Thread Alan Bateman
On 27/03/2024 17:05, Sergey Chernyshev wrote: In the discussion of .ofLiteral() it was not concluded that .ofPosixLiteral() would be insecure or undesirable. From the 'security issues' point of view, it is a new method, it won't change the behavior of old apps. If any code (a csrf filter)

Re: InetAddress API extension proposal

2024-03-27 Thread Sergey Chernyshev
Hi Bernd, Thank you for your comments! inet_addr() is POSIX.1, please see https://pubs.opengroup.org/onlinepubs/9699919799/functions/inet_addr.html In its common implementation inet_addr() is just u_long inet_addr(cp) register const char *cp; { struct in_addr val;

Re: InetAddress API extension proposal

2024-03-26 Thread Alan Bateman
On 27/03/2024 01:51, Sergey Chernyshev wrote: Hello Core Libs Dev team, I would like to propose a PR to extend the InetAddress API in JDK 23, namely to provide interface to constructing InetAddress objects from literal addresses in POSIX/BSD form (please see the discussion [1]), to the Apps

Re: InetAddress API extension proposal

2024-03-26 Thread Bernd Eckenfels
Would be helpful to point to the posix standard/requirement which mandates this. Do you mean a single Unix api description or a posix command spec? I don’t think I know of any such things. Wikipedia claims A POSIX-conforming variant of inet_aton, the inet_pton() function, supports only the four