Re: Limiting RMI to localhost



haimcn@xxxxxxxxx wrote:
I'm writing a big application that I divide into 2 processes (server
and interface) with RMI to communicate between them.
I would like to limit the access to the server only from the interface
process and also only from the local machine.
Is there a way to limit RMI to localhost only?

I cannot block all sockets outside the machine since I use them in the
server process.

Simply block the RMI port with the firewall from non-localhost access. You'll have to look the port up, I don't remember which one it is off the top of my head. It'll be a different port than the ones you expose "in the server process".

This is an OS-specific operation, but most Windows "personal firewall" products and any Linuxen have the capability.

--
Lew
.



Relevant Pages

  • Dungeon Siege - Server behind Sygate NAT with Port Forwarding - HELP!
    ... I have an in depth NAT question with port forwarding from LAN/WAN ... for the game on the server. ... first, and then my LAN clients connect, they will lose sync after about 2 ... coming in on DSL interface? ...
    (comp.security.firewalls)
  • Re: Unable to access private network from the VPN (NAT)
    ... Port forwarding/filtering is a completely ... why does the server have two interfaces in the same IP ... This extends the VPN ... The first interface is ...
    (microsoft.public.win2000.ras_routing)
  • Re: RRAS Question for you routing gurus
    ... on the publicly accessible server to the public interface and put the one IP ... to the port being used. ... outgoing traffic and will give the LAN clients Internet access. ...
    (microsoft.public.windows.server.networking)
  • Re: RDP Port (un)binding to specific interface?
    ... If you run Terminal Services Configuration, ... RDP-Tcp properties to only listen on a particular interface. ... > server to specified external IPs. ... > the port on the external interface is being used by another application. ...
    (microsoft.public.windows.terminal_services)
  • Re: RRAS Question for you routing gurus
    ... to the port being used. ... (ie one to one NAT). ... server you do not need to use services and ports at all. ... Select this interface as the public interface in NAT and check the ...
    (microsoft.public.windows.server.networking)