Mike Bremford
Bit poster
Hi there
I have Parallels 4 installed in my machine, and although I'm not running Parallels currently I do have the prl_disp_service daemon running in the background. Not a problem except it's running as root, and it's listening on port 64000 on all network interfaces.
From a security point of view this isn't ideal. I use parallels locally with Shared Networking, and I don't see why this requires me to open a socket and listen to connections from outside my physical machine. Can someone at parallels explain what's going on, why it's listening to all interfaces rather than localnet and/or the parallels virtual interfaces, and how to close this socket unless I actually have a VM up?
Thanks, Mike
I have Parallels 4 installed in my machine, and although I'm not running Parallels currently I do have the prl_disp_service daemon running in the background. Not a problem except it's running as root, and it's listening on port 64000 on all network interfaces.
From a security point of view this isn't ideal. I use parallels locally with Shared Networking, and I don't see why this requires me to open a socket and listen to connections from outside my physical machine. Can someone at parallels explain what's going on, why it's listening to all interfaces rather than localnet and/or the parallels virtual interfaces, and how to close this socket unless I actually have a VM up?
Thanks, Mike