The use of multiplexing to the client bypasses intended security
checks. It was initially introduced to allow callbacks to applets
which were impossible to do because the Netscape browser's security
manager did not allow applets to listen on a socket on an anonymous
port.
Client-side multiplexing should not be initiated and support
for it should be removed. The server-side multiplexing should remain
to be backwards compatible with earlier releases that use client-side
multiplexing.
checks. It was initially introduced to allow callbacks to applets
which were impossible to do because the Netscape browser's security
manager did not allow applets to listen on a socket on an anonymous
port.
Client-side multiplexing should not be initiated and support
for it should be removed. The server-side multiplexing should remain
to be backwards compatible with earlier releases that use client-side
multiplexing.
- relates to
-
JDK-8087189 RMI server-side multiplex protocol support should be removed
- Resolved
-
JDK-4161204 multiplexed connections does not work across firewall
- Closed
-
JDK-4145254 Stream-mode connections should be closed when the multiplexer is needed
- Closed
-
JDK-4257730 Client initiated multiplex RMI socket connectivity disabled in JDK 1.2.2
- Closed