Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
4.1.0
-
None
Description
The use case is setting up an RMI server on a fixed port (using <amq:managementContext rmiServerPort="xxx">) in order to pass through a firewall. This RMI server doesn't honor the com.sun.mangement.password.file et al environment variables. Simply guessing the hostname and port (and the default port being a well known port, meaning "no guesswork at all") is enough to take full control of AMQ.
Further, but somewhat unrelated, if one sets up a password protected Tiger JMX MBean server, AMQ can't configure it, giving a read only error message.