-
Enhancement
-
Resolution: Won't Fix
-
P4
-
None
-
5.0
-
generic
-
generic
Currently, binding to any "reserved" or "privileged" port (0-1023)
requires starting the JVM as root, which is unacceptable in many
circumstances. There may be workarounds available such as starting the
JVM as root, creating a ServerSocket for the desired privileged port,
and then changing the JVM to a non-root user while holding on to the
previously generated ServerSocket, but this would complicate many
startup procedures.
Our specific use case where the above feature would be required is S1AS 8, which users will not want to run as root. In addition, competing technologies such as the Apache webserver already support this.
requires starting the JVM as root, which is unacceptable in many
circumstances. There may be workarounds available such as starting the
JVM as root, creating a ServerSocket for the desired privileged port,
and then changing the JVM to a non-root user while holding on to the
previously generated ServerSocket, but this would complicate many
startup procedures.
Our specific use case where the above feature would be required is S1AS 8, which users will not want to run as root. In addition, competing technologies such as the Apache webserver already support this.
[JDK-4827289] Provide ability to bind to privleged ports as non-root user
BT2:EVALUATION
This is a very tricky issue and requires support from the platform which is lacking at the moment on most supported platforms.
Also, it does raise a few security concerns, these ports are privileged for a reason.
Anyway, it's too late for consideration in Tiger. Will examine in future version.
###@###.### 2003-07-23
This is a very tricky issue and requires support from the platform which is lacking at the moment on most supported platforms.
Also, it does raise a few security concerns, these ports are privileged for a reason.
Anyway, it's too late for consideration in Tiger. Will examine in future version.
###@###.### 2003-07-23
so closing as WNF